OpenEuphoria

RE: A sequence, by any other name

• Posted by Jonas Temple <jktemple at yhti.net> Feb 28, 2001
• 498 views

matthewwalkerlewis at YAHOO.COM wrote:
> I'm not sure what exactly to do about the sequence datatype, since 
> there's
> no real parallel in other DBMS's.  Probably, it would treat those as 
> invalid
> fields for non-Eu processes (I think someone wanted to access EDS 
> through
> Delphi), while an Eu-based process could handle them just fine.  There'd 
> be
> several ways to get around this, though, including creation of subfields 
> or
> compressing a sequence before saving it to the record, and decompressing 
> in
> whatever way made sense.
> 
> I'll probably handle this (API-wise) along the lines of ODBC--maybe even
> write an ODBC driver for EDS!--where you can get descriptions of the 
> various
> fields, including names and datatypes.
> 
> Also, I've just about got the ODBC code set up to return less than full
> recordsets.  It changes the way you interface with the lib, but not too
> dramatically.

Geez, Matt, where do you find the time?  I have been working on some Eu 
stuff for months now and can barely find time.  

For the EUSQL and EDS ODBC, how about this:

- Include the data type as part of the TABLEDEF information, as you 
stated you are considering.
- Since ODBC doesn't handle sequences how about the EUSQL/EDS ODBC 
driver expand the record down to the lowest sequence?  Heck, you could 
even write the ODBC driver for EDS and not have to continue to support 
EUSQL.  For example, take the following sequence:
TABLEDEF:
{{"First Name"}, {}},

{{{"First Name"},{"Last Name"}},{{"123"},{"456"},{"7890"}}} 
   Full Name                       Phone numner
a select * would return:
{"First Name", "Last Name", "123", "456", "7890"}