> > PySQLite doesn't populate some of the attributes that are needed for > > the getStructureDescription() method. After all, when you create a new > > record, Python needs to know the fields and the data types of each in > > order to create a representation of that new record, and PySQLite > > doesn't provide that information. Perhaps we can look into coming up > > with a workaround in dbSQLite.getStructureDescription(). > > Yep, this is something that is *really needed* and *very badly*. We > actually need to be able to get the full structure of the query passed > from the backend, so we have an idea what the field types are even if > the query returned zero records. > > May not be possible (I at least can't think of a way, even for MySQL > which I know really well)... you can always get the types of columns > using DESCRIBE <tablename> but I don't know how to get types of derived > fields as MySQL would have returned them had records been returned. > > And, more importantly, getting SQLite working in this regard as well.
I have an idea that could work. I wanted to put dTable into bizobj somehow. If the bizobj had access to the dTable definition of the table, would it then have all the info it needed? Then the primary use of dTable would be so the bizobj knows about the table. And as a feature, it could create the table if it doesn't exist and if it has access. Would this be too messy or require Dabo uses to do too much recoding? -- -Echo _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
