Hi Brian, You would have to create your view in SQL directly (through raw SQL). Once the view is created you should be able to create a web2py model for it and use the web2py DAL on it as a normal table (using 'select'). I do not use Postgres but I believe that it right. Anyhow, it would be trivial to try it, assuming that your Postgres DB is conveniently available. Regards, D
On Feb 24, 11:06 am, darkblue_b <[email protected]> wrote: > Hi All- making some progress here in week 1 with web2py... > I wrote my postgres database first, and generated the model from it.. > and that is working well .. > But I have one *postgres* view, which is about 5 joins.. I dont yet > understand.. > Do i have to write this out in the web2py *QL, or can I execute sql > and return it somehow .. > (I do not yet understand how I specify response._vars and such for > web2py views... > - will re-read while researcing ) > > the ideal interface would be something like : > choose a concat of date + company from a popup at the top.. > or, heck, just the pkey for now > get a collection of 250 formatted rows in a scrolling window below, > per popup choice > The rows are filled in by 3 joins from a central table to 3 fk_tables > The popup choice fills in company info in the header.. > > thanks in advance for leads on this.. > -Brian
