> > > > Umm, OK, I think I figured part of the answer...for PP DBI, FETCH() is in > > DBI::PurePerl, but for mainstream DBI, its in XS code, yes ? > > That latter throws in some wrinkles... > > Ignore that for now. Just write it as a perl sub and we can look at > integrating it if/when we're all happy with what it does. > > > Also, can anyone point me to a copy of ISO/ANSI SQL std. that describes > > the type characteristics of some of the newer/more complicated types, > > esp. REF, ARRAY, MULTISET, UDT, LOCATOR, ROW, and the INTERVAL > > items as well (I know how my DBMS flavor handles INTERVAL declarations, but > > am not certain what the "standard" is). Specifically, I'm looking for which > > types have precision and scale, and where those items would be applied > > eg, "DECIMAL(precision, scale)" vs. > > "INTERVAL HOUR(precision) TO SECOND(scale)" > > > > (Is that how other drivers use PRECISION and SCALE with INTERVAL types ?) > > I was wondering how soon you'd start facing the more tricky cases :) > > Tim.
I found an ISO SQL spec (for SQL-99 anyway... has DBI declared any conformance level at this point ?) And my interpretations of type string formats seem pretty conformant. However, the "exotics", e.g. ROW, GUID, UDT, etc. will likely have only generic defaults for obvious reasons (questions? just read the spec), but INTERVAL defaults will behave pretty much as I described. Quick poll: how many drivers supply a PRECISION value for INTEGER, REAL, FLOAT, DOUBLE PRECISION ? The std. indicates they can have precision... Dean Arnold Presicient Corp. www.presicient.com
