The reason you have to define tables in dal is that a string field in the database may be just a string field but may be a password, or a filename at the web2py level. web2py needs to know. If you do not care and you have no plans to move to any other db engine, than there is nothing wrong in using raw sql. SQLFORMs and grid will not work.
On Jan 24, 3:54 pm, Nomad <[email protected]> wrote: > Im looking for feedback on if this is poor practice > > situation: i have an existing service that uses a sqlite3 database i was > asked to port to a webapp. Being semi-familiar with MVCs and web2py i > decided to give this a go. We have functions defined in python to return > the expected data already.the app itself has 18+ months worth of data > > problem: reading up on the pdf manual (we written btw) it seems like using > a DAL i have to define every naunce of the current database. Also, there is > strong change of data type changing based on the description. > > Is it bad practice just to import sqlite3 and call it a day ? Is there any > strong advantage to using a DAL ? or am i simply over thinking the problem ? > > feed back would be appreciated
