The way to fix it is to use SQLField(...,"reference [table]") instead of SQLField(...,db[table]) This syntax is already supported and it must be required for lazy tables.
It is still a problem to make lazy evals work with IS_IN_DB and IS_NOT_IN_DB anyway, we made so many improvements that perhaps lazy evals will be less important... let's way for more tests from Alexey. Massimo On Jun 7, 5:04 am, vihang <[email protected]> wrote: > Hans, that won't work if you are refering to the same db which is > being created (circular reference issue)... > > On Jun 6, 11:23 pm, Hans Donner <[email protected]> wrote: > > > yep, > > add requires=IS_NOT_IN_DB(db,db.some_table.field1) > > in the SQField(....) statement as an argument > > > On Sat, Jun 6, 2009 at 9:17 PM, vihang<[email protected]> wrote: > > > > Very interesting mod. > > > > @Massimo, as mentioned about the requires statement, is there a way to > > > address the following directly in the field definition? > > > > db.some_table.field1.requires = IS_NOT_IN_DB(db,db.some_table.field1) > > > > On Jun 6, 7:51 pm, mdipierro <[email protected]> wrote: > > >> I think it is a great idea. > > >> , > > >> Anyway, I would like to remind people the following web2py command > > >> line option > > >> -F PROFILER_FILENAME, --profiler=PROFILER_FILENAME > > >> profiler filename > > > >> Massimo > > > >> On Jun 6, 10:17 am, DenesL <[email protected]> wrote: > > > >> > Very interesting. > > >> > How about creating a test case app that people could run to report > > >> > performance results on different platforms and CPUs?. > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" 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 -~----------~----~----~----~------~----~------~--~---
