On Aug 31, 2011, at 3:50 PM, John Fabiani wrote:
> Rather than attempt to create a universal dbODBC.py where I attempt to deal
> with each database unique requirements, i.e. data types, getting the last
> insert PK, limits, etc.. This would be a match to what we are currently doing
> for each of the supported databases (postgres, mssql, mysql) currently.
Let's keep it simple first. Go with a generic dbODBC.py, and make it
specific to MSSQL. Once that's working, see what would be involved in adding
support for VFP (or some other ODBC backend). If there is more involved than
handling a few differences in code it might be good to get more granular than
that, but we'll still need an ODBC superclass to handle the common code, which
is what we're doing with the other servers you mention. We have the dBackend
class that holds all the common behavior, and when a specific backend deviates
from that, we break that code into the subclass for that server type.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
Searchable Archives: http://leafe.com/archives/search/dabo-dev
This message:
http://leafe.com/archives/byMID/[email protected]
