Reading through Ch 6: - p143 - perhaps a note that the term SQL is genericly used (GAE does not use SQL) - p144 - bit confusing to still have SQLRows, ...Storage, ...Query, ...Set and ..Xorable; perhaps prefix them with DAL insetad of SQL - p145 - the SQLXorable description is unclear. I still cannot explain this to a non-developer (even when I peek at the data). Is it relevant here? - p145 - the image needs updating (still uses SQLDB) - p145 - the image is now confusing, just before the Field is indicated as to be derived from Xorable and in the pictures it looks like it is the reverse. I believe the image is trying to convery another story, but it is not clear what story and where it is told - p146 - assume it is on the default port, but some connection strings still have a port in them - p146 - firebird has a user insteda of a username - p147 - halfway it is mentioned that DAL can make multiple connections to different databases. Please refer to a section where this will be described - p147/148 - migrations may need a sepcial paragraph header, as it is quite an important subject - p147/148 - perhpas also mention good practice re the usage in production and development environments - p148- the coding example halfway still uses SQLField - p148 - uploadfield or " uploadfield", the usage of quotes are not always consistent - p148 - mention of SQLFORM, see earlier comment - p149 - the italic section, why is the distinction important? - p149 - a list of default widgets - where will it be listed? - p150 - second bullit, " will di displayed" - p150 - "25% more storage" / "reduced the amount of data" seems to contradict, and could use an explanantion - p151 - id's starting at 1, is backend specific (not on GAE) - p151 - halfway, still mention SQLField - p152 - restrats at 1 - is backend specific (not on GAE) - p153 - commit/rollback - is backend specific (not on GAE) - p153/ 154 - executesql / indices. Text is contradicting, mention with executesql the usage for selects is normally not needed, but is more common for indexes - p154/155 - "this is one the way .. ", consider revising this part. web2py follows the design for a technical key, which is a good practice. many db's use only logical keys, which is another practice but (currently?) not supported by web2py if it doesn't have a technical key as well - p156 - the one-line examples seem to be chained, could perhaps be made more expicit in the text for those readers doing only the reading and not the live examples - p156 bottom - field selection is backend specific, gae works differently - p157, the example at the bottom; can this be typed into the interpreter? - p157, doing this kind of db in a view is not by everybody considered good MVC practice - p158, orederby etc - is backend specific (not on gae) - p158, " an filed is derived from an sqlxorable" this seems to come from nowhere/blue sky - p158, logical operators. Perhpas mention explicitly that AND and OR are not supported due to python restrictions - p160, relations - not on gae - p161, INNER OUTER JOIN ? - p165, helpers? Perhaps make a reference to a previous chapter
Hans On Sat, Jul 11, 2009 at 6:33 PM, Jose<jjac...@gmail.com> wrote: > > > > On 11 jul, 14:57, Massimo Di Pierro <mdipie...@cs.depaul.edu> wrote: >> Chapters 7 and 8 have been revised including corrections from Mr >> Admin, Fran and Jonathan. >> >> web2py_manual_678.pdf >> 1982 KVerDescargar > > Massimo > > In the page 146: > > The ports of mysql and postgre are equal. > In firebird already it is not necessary to put the port 3050. > > Jose > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
