You could put all of them (and more) in the Rows class but you would take a performance hit since the processing would be handled by the web server after the select is done and not the database or...put all of them in Field as well and tweak SQL_DIALECTS to flag operations as unsupported and throw an error.
On Oct 13, 10:34 pm, Thadeus Burgess <[email protected]> wrote: > Could we write python wrappers around the functions that are not supported > for that particular backend? > > -Thadeus > > On Tue, Oct 13, 2009 at 10:12 PM, mdipierro <[email protected]> wrote: > > > On Oct 13, 9:02 pm, "mr.freeze" <[email protected]> wrote: > > > This has probably been asked before but why doesn't the Field class > > > have these?: > > > no > > > > avg, format, round, mid, len, first, last > > > > Is it because they are not common to all databases? > > > yes > > > probably avg and round should be implemented since they are common. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
