Is there a way (in RB 5.2 or later - language-wise) to make a
class act like a data source (i.e. it can act as a back-end for an
SQL query, and return a RecordSet (or the modern equivalent)?) Has
anyone filed a feature request for this?
IMHO, it'd be better if the whole database thing were separated
into two parts; the 'model' back-end which would be provided, or
could be made as a set of classes that implement an interface (or set
of interfaces) that would allow the 'front-end' SQL parser to 'do'
the SQL things one would expect. Then, one could use both the front-
and back-ends as provided, write their own back-end, write their own
front-end, or subclass either.
The problem now is that all the database solutions are monolithic;
whether it's a plug-in, or a built-in class, they all handle both the
front- and back-ends of the process, making it difficult to get a
byte in edgewise... (okay, bad pun.)
The two-part scheme - it seems - would be more flexible and
extendable from what I can see. You could even hang a set of classes
to interpret a custom file format (XML, or CSV, or whatever) onto
Valentina/RBDB/MySQL/ODBC/etc... in such a way that they could be
"SQL"d (at least in a read-only fashion, if not R/W.)
At the very least, is it feasible to 'hand construct' a RecordSet?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
