Bug #123

Bug #114: contracts and marketorders won't update

Market Orders: MySQL wrong data type in range...

Added by tash about 1 year ago. Updated about 1 year ago.

Status:Closed Start date:Apr 23, 2012
Priority:Normal Due date:
Assignee:tash % Done:

100%

Category:app-accounting Spent time: -
Target version:2.0.4.1
Detected Version:2.0.0 Python Version:al

Associated revisions

Revision 744:88bcc77c77af
Added by tash about 1 year ago

Bug #123: changed range field to Integer (may be -1) which MySQL doesnt like.
Added migration

History

#1 Updated by tash about 1 year ago

  • Description updated (diff)

whoops, wrong description.. see parent task ^^

#2 Updated by tash about 1 year ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

#3 Updated by tash about 1 year ago

  • Target version changed from 2.2.0 to 2.1.0

#4 Updated by diabeteman about 1 year ago

  • Target version changed from 2.1.0 to 2.0.2

#5 Updated by diabeteman about 1 year ago

  • Description updated (diff)

#6 Updated by diabeteman about 1 year ago

  • Description updated (diff)

Apparently there are other fields to modify. I have the same kind of error with pg (after the 0003 migration of accounting)

2012-04-25 01:26:05,988 [INFO ] ecm.plugins.accounting.tasks.marketorders - fetching /corp/MarketOrders.xml.aspx...
2012-04-25 01:26:06,254 [DEBUG] ecm.plugins.accounting.tasks.marketorders - parsing api response...
2012-04-25 01:26:06,266 [ERROR] ecm.apps.scheduler.models - 
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/ecm-2.0.1-py2.7.egg/ecm/apps/scheduler/models.py", line 113, in run
    func(**args)
  File "/usr/lib64/python2.7/site-packages/ecm-2.0.1-py2.7.egg/ecm/plugins/accounting/tasks/marketorders.py", line 47, in update
    processOrders(ordersApi.orders, api_conn)
  File "/usr/lib64/python2.7/site-packages/ecm-2.0.1-py2.7.egg/ecm/plugins/accounting/tasks/marketorders.py", line 63, in processOrders
    write_orders(added_orders, removed_orders)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/transaction.py", line 209, in inner
    return func(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/ecm-2.0.1-py2.7.egg/ecm/plugins/accounting/tasks/marketorders.py", line 75, in write_orders
    order.save()
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/models/base.py", line 463, in save
    self.save_base(using=using, force_insert=force_insert, force_update=force_update)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/models/base.py", line 551, in save_base
    result = manager._insert([self], fields=fields, return_id=update_pk, using=using, raw=raw)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/models/manager.py", line 203, in _insert
    return insert_query(self.model, objs, fields, **kwargs)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/models/query.py", line 1576, in insert_query
    return query.get_compiler(using=using).execute_sql(return_id)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/models/sql/compiler.py", line 910, in execute_sql
    cursor.execute(sql, params)
  File "/usr/lib64/python2.7/site-packages/Django-1.4-py2.7.egg/django/db/backends/postgresql_psycopg2/base.py", line 52, in execute
    return self.cursor.execute(query, args)
DatabaseError: integer out of range

#7 Updated by diabeteman about 1 year ago

  • Status changed from Resolved to In Progress
  • Target version changed from 2.0.2 to 2.0.3
  • % Done changed from 100 to 50

#8 Updated by diabeteman about 1 year ago

  • Target version changed from 2.0.3 to 2.0.4.1

#9 Updated by tash about 1 year ago

i will look into it ... But i think it is related to range field. Changing it to Bigintfield will hopefully work for both mysql & psql.

#10 Updated by tash about 1 year ago

Range is the only int. Its likely that i might need to change it to bigintegerfield to make work on both mysql & psql.

#11 Updated by tash about 1 year ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

PositiveIntegerfields changed to BigInt, tested with mysql, postgres and sqlite

#12 Updated by diabeteman about 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF