open an issue with a model and the query to reproduce ...... so it gets
tracked (and fixed)
On Thursday, March 7, 2013 12:30:16 AM UTC+1, chicks wrote:
>
> Changed to this to fix:
>
> fields = db.projects.prj_type,db.projects.prj_name, \
> db.projects.prj_environment,db.projects.prj_zone, \
> db.projects.prj_host,db.projects.prj_port, \
> db.projects.prj_instance,db.projects.prj_app_type, \
> db.projects.prj_application, \
> db.projects.prj_dbhost,db.projects.prj_dbinstance
> rows = db( query ).select(*fields, orderby=orderby)
> Hope it stays fixed...
>
> On Wednesday, March 6, 2013 11:11:14 AM UTC-8, chicks wrote:
>
>> Been running on 2.0.9 for some time, trying to update to 2.4.2, but some
>> query returns have changed, breaking SQLTABLE() attempt.
>>
>> An Oracle query that returns this on 2.0.9:
>> <Row {'prj_zone': 'ETGA1', 'prj_app_type': 'ANI', 'prj_instance': 'ani',
>> 'prj_name': 'ETGA', 'prj_host': 'ZUATAPP6', 'prj_application': 'ANI',
>> 'prj_environment': 'MNF', 'prj_dbhost': 'uatdb3', 'prj_dbinstance':
>> 'gamnf', 'prj_type': 'ET', 'prj_port': None}>
>> returns this on 2.4.2, which breaks SQLTABLE():
>> <Row {'_extra': {'projects.prj_type, projects.prj_name,
>> projects.prj_environment, projects.prj_zone, projects.prj_host,
>> projects.prj_port, projects.prj_instance, projects.prj_app_type,
>> projects.prj_application, projects.prj_dbhost, projects.prj_dbinstance':
>> 'ET'}}>
>> What's up with the "_extra"???
>>
>> Thanks,
>>
>> Chuck
>>
>
--
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
