hi- thanks for this continuing thread.. I thought about it a bit, and yes, I see there is a great fundamental divide between people new to web2py jumping in and trying to make things work with executesql() and such, and on the other hand using the framework to do what it does.. that's true for me, certainly. So the answer that seemed like a non-answer to me was actually addressing a fundamental, although in paucity of expression, rather than the details at hand. I am about to sit down to write the view.. more later.. -Brian
On Feb 26, 5:39 am, DenesL <[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 .. > > 1) build your models in Web2py and let it create your DB schema > > > 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 .. > > 2) try to first use Web2py DAL. > > Maybe his answer was not what you expected but it is surely related > and correct. > > > (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.. > > I suggest posting the table details so that anyone willing to help can > reply with web2py specific code samples. > > > thanks in advance for leads on this.. > > -Brian
