Could help to understand if you send the model... For postgres views you cand define them as a table in web2py model... You will not be able to create, update and delete obviously, but read, select will be fine. So if you it is more easier for you like me in a first time to write SQL then you can translate your query into web2py query later. Or you can also use RAW SQL into web2py, but it is discouraged.
Richard On Thu, Feb 24, 2011 at 6: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 > >
