On Thursday, January 22, 2015 at 3:30:25 PM UTC-8, Dave S wrote: > > > > On Thursday, January 22, 2015 at 12:21:31 AM UTC-8, Y wrote: >> >> Wouldn't step 2 be designing the database itself? >> >> > If a database was part of the solution, then a first cut at the database > would be a reasonable step 2. > > Step 1 should tell you if a database is part of the solution. > > Web2py makes using database in your server easy, but it also works for > other types of servers > (dashboards, control interfaces, etc). > > In the spirit of rapid development, I would expect that the database > design may evolve as a result of early trials. > > Of course, some designs involve working with a database that is *already *designed, and your job is to integrate it.
/dps -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
