Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Niphlod
me neither. Lately I try to assume the fact that something is stable only if it's tested. If it isn't, then it may change in a while, so I don't write code depending on it. Fortunately as_json() is not documented in the book (hence "experimental" at least in theory) but I'd argue that someone b

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Anthony
It does look like a significant change was made to Row.as_json -- previously it did pull the items out of _extra, but now leaves _extra in place. Not sure why. Anthony On Wednesday, June 4, 2014 6:34:35 AM UTC-4, Niphlod wrote: > > Does this mean that your code relied on rows.json() and now the

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Niphlod
BTW: I think that if you download the latest version (i.e., the latest source code) you'd have no issues with SQLTABLE because of a patch has been included for it on 2014-04-24. On Wednesday, June 4, 2014 12:34:35 PM UTC+2, Niphlod wrote: > > Does this mean that your code relied on rows.json() a

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Niphlod
Does this mean that your code relied on rows.json() and now the output is different ? In other words: can you please state what your application needs from 2.5.1 to work and doesn't with 2.9.5 ? Did you try with the trunk version ? On Wednesday, June 4, 2014 11:13:17 AM UTC+2, Massimiliano wrot

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Massimiliano
I think that is the problem. Data from rows.json() Look at the data structure: version 2.5.1 u'[{"SUM(qviewriepilogoprevisioni.motrici)": 0, "zona": "ABRUZZO", "SUM(qviewriepilogoprevisioni.bilici)": 2, "SUM(qviewriepilogoprevisioni.abbinati)": 0, "tratta": "ASCOLI (Ascoli Piceno)"}, {"SUM(qvie

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Niphlod
I don't know what to suggest unless you show some code. On Wednesday, June 4, 2014 10:23:29 AM UTC+2, Massimiliano wrote: > > I think I explained the problem in the wrong way. > > Before, with the old version of web2py some procedures that make use of > datatable worked very well. > Today we miss

Re: [web2py] Re: TABLE and aggregate fields

2014-06-04 Thread Massimiliano
I think I explained the problem in the wrong way. Before, with the old version of web2py some procedures that make use of datatable worked very well. Today we miss some fields... aggregate fields. So I was looking for an hint to make the system work again with little effort :D Thank you On Tue

[web2py] Re: TABLE and aggregate fields

2014-06-03 Thread Niphlod
it's not a problem. we just changed the way a Rows class gets represented (printing resultsets with 1k rows was kynda lame ^_^) if you do print rows things "change", but for row in rows: print row doesn't change a bit. On Tuesday, June 3, 2014 12:53:08 PM UTC+2, Massimiliano wrote: > >