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
building an API out of it didn't notice the "sudden change" :D .
On Wednesday, June 4, 2014 2:08:51 PM UTC+2, Anthony wrote:
>
> 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 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 wrote:
>>>
>>> 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(qviewriepilogoprevisioni.motrici)": 0, "zona": "ABRUZZO",
>>> "SUM(qviewriepilogoprevisioni.bilici)": 3,
>>> "SUM(qviewriepilogoprevisioni.abbinati)": 0, "tratta": "C. ABRUZZO
>>> (Pescara)"}]'
>>>
>>> version 2.9.5 Now aggregate fields are under "_extra"
>>>
>>> [{"cooptratte": {"tratta": "ASCOLI (Ascoli Piceno)"}, "coopzone":
>>> {"zona": "ABRUZZO"}, "_extra": {"SUM(qviewriepilogoprevisioni.bilici)": 1,
>>> "SUM(qviewriepilogoprevisioni.motrici)": 0,
>>> "SUM(qviewriepilogoprevisioni.abbinati)": 1}}]
>>>
>>> Thank you
>>>
>>> On Wed, Jun 4, 2014 at 10:47 AM, Niphlod <[email protected]> wrote:
>>>
>>>> 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 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, Jun 3, 2014 at 5:26 PM, Niphlod <[email protected]> wrote:
>>>>>
>>>>>> 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:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I've an application in production with 2.5.1-stable+timestamp.2013.
>>>>>>> 06.06.15.39.19, and I would like to update at the newest
>>>>>>> web2py 2.9.5-stable+timestamp.2014.03.16.02.35.39, but I could a
>>>>>>> problem with aggregate fields.
>>>>>>>
>>>>>>> That is what's happen:
>>>>>>>
>>>>>>> If I print my Rows var I get:
>>>>>>> print rows:
>>>>>>>
>>>>>>> zone.zona,tratte.tratta,SUM(qviewriepilogoprevisioni.bilici),SUM(
>>>>>>> qviewriepilogoprevisioni.motrici),SUM(qviewriepilogoprevisioni.
>>>>>>> abbinati)
>>>>>>> ABRUZZO,ASCOLI (Ascoli Piceno),3,0,0
>>>>>>> ABRUZZO,C. ABRUZZO (Pescara),2,0,0
>>>>>>> ABRUZZO,S.BENEDETTO (),1,0,1
>>>>>>>
>>>>>>> BUT if I do something like that:
>>>>>>>
>>>>>>> TABLE(rows)
>>>>>>>
>>>>>>> I got ONLY the 2 fields zone.zona,tratte.tratta
>>>>>>>
>>>>>>> With the old web2py version this wasn't happen.
>>>>>>> Where can I start to look at this problem?
>>>>>>>
>>>>>>> Thank you
>>>>>>>
>>>>>>> --
>>>>>>> Massimiliano
>>>>>>>
>>>>>> --
>>>>>> Resources:
>>>>>> - http://web2py.com
>>>>>> - http://web2py.com/book (Documentation)
>>>>>> - http://github.com/web2py/web2py (Source code)
>>>>>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>>>>>> ---
>>>>>> 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/d/optout.
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Massimiliano
>>>>>
>>>> --
>>>> Resources:
>>>> - http://web2py.com
>>>> - http://web2py.com/book (Documentation)
>>>> - http://github.com/web2py/web2py (Source code)
>>>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>>>> ---
>>>> 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/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Massimiliano
>>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
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/d/optout.
