On 8/31/11 1:50 PM, John Fabiani wrote: > I currently have the pyodbc accessing MsSQL and all seems to work very well > from a hand coded form. I have not attempted to get the CxnEditor working, > ClassDesigner, or AppWizard yet.
Right: don't attempt to get the UI tools working until the basic code-only interface is working. > I'm wondering if it might be a better idea to create unique odbc interfaces > for each of the databases we are going to support using pyodbc. IOW's I'd > like to see: > dbMsSqlODBC.py > dbDbfODBC.py > dbOracleODBC.py > etc... Unless I'm misunderstanding you, isn't almost exactly what I proposed in my mail this morning where I say: """ Dabo would benefit immensely with a pyodbc wrapper. I think though we should define specific wrappers like: mssql_odbc vfp_odbc dbase_odbc and perhaps also add a plain-vanilla odbc wrapper which needs to be subclassed by the appdev for a given proprietary API. """ > 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. > > The difference would be that each of the files would use the same pyodbc.py > but would have different method details (the code). > > Thoughts or suggestions please! Sounds like you are on the right track. Paul _______________________________________________ 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]
