references and id got "upgraded" cause before with high id numbers you could end up with exceptions. In any case, you're relying on the default formatting as a string of a value .... for whatever value out there, especially if you need to pass it to javascript, always do EXPLICIT conversions in your app code.
Il giorno mercoledì 19 giugno 2013 10:13:43 UTC+2, palomar ha scritto: > > why I shouldn't convert it to an INT? It is the ID of my table and I need > it as integer (as on the preview version) to send it to my javascript > function... > > Il giorno martedì 18 giugno 2013 18:40:06 UTC+2, Derek ha scritto: >> >> If you aren't using google app engine, then that should be okay. However >> if you are, you shouldn't convert it to an INT because you'll get errors. >> >> The "L" means it's a LONG and not an INT. >> >> On Tuesday, June 18, 2013 7:11:14 AM UTC-7, palomar wrote: >>> >>> I've just updated to 2.5.1 and I found this problem: >>> Inside my site have a google map and I need to add an array with >>> several marker; >>> in my controller I have a simple query with a cycle >>> def mappa: >>> markers=[] >>> for row in db().select(db.produttori.ALL): >>> markers.append([row.id, row.lat, row.lng]) >>> return dict(markers=XML(*[markers])) >>> >>> and I obtein ID + L, like this: >>> [1L, '12.5', '7.6'] >>> >>> so I need to do int(row.id) >>> In the older version worked well... >>> s. >>> >>> -- --- 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.
