Though to be fair, the documentation simply says that id fields are auto-incrementing *integers*, and for many years, they were just int's on the web2py side, so it probably wasn't reasonable to expect everyone to do int(row.id) everywhere instead of just row.id in anticipation of some possible future change from int's to long's. Anyway, what's done is done, and reverting would break backward compatibility for many newer apps. Shouldn't be too hard to fix in cases where this is an issue.
Anthony On Friday, June 21, 2013 2:29:33 AM UTC-4, Niphlod wrote: > > it's not a major change. You're the one writing programs that are relying > on the default serialization instead of defining your own. > > Il giorno giovedì 20 giugno 2013 23:14:16 UTC+2, Richard ha scritto: >> >> Can someone point me out change log... I didn't see this one... >> >> http://web2py.com/init/default/changelog >> >> I think it is not in the change log and it is not acceptable.... >> >> Thanks >> >> Richard >> >> >> On Wed, Jun 19, 2013 at 9:23 AM, palomar <[email protected]> wrote: >> >>> thanks for your reply! >>> >>> -- >>> >>> --- >>> 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. >>> >>> >>> >> >> -- --- 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.
