On Monday 22 January 2007 13:35, Ed Leafe wrote: > On Jan 22, 2007, at 3:42 PM, johnf wrote: > > The request was support for "system defined function" data types: > > They all start with 'reg". Postgres calls them "OID alias types" > > And in > > general deal with the 'OID' data type. > > Then you need to run some queries with psycopg and find out how > those types are being converted into Python data, as well as the way > it is documented in psycopg's cursor.description value. Once we know > that, we can figure out how to handle them in Dabo. Remember, Dabo is > Python-only; it has nothing to do with anything in PostgreSQL. > > > To be truthful I real don't understand the dabo data types - other > > than they > > are just simple types (string, numeric,float,bool). > > All of the dbapi programs, such as psycopg, translate the data types > used in the backend into Python types. That's part of what they do. > > The Dabo data types are simply those Python types that correspond to > database values, along with a one-character identifying code that is > a link back to the info returned by the dbapi package. For example, > 'char', 'varchar', 'tinytext', 'text', 'mediumtext' and 'longtext' > are all distinct datatypes in MySQL, but they all are handled as > unicode values in Python. The only reason we distinguish between > these as either 'C' or 'M' in Dabo is so that things such as the > datanav framework knows whether to use a textbox or an editbox. > > -- Ed Leafe > -- http://leafe.com > -- http://dabodev.com
I have been running simple queries. But it seems possible to return different types for similar queries. Not only that but I can't get some of them to return anything. One actually returns a tuple. As far as only using python types - what type was used for the binary stuff you did with images? -- John Fabiani _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
