Re: to_reference
Paolo Redaelli <[email protected]> Mon, 29 May 2006 08:49:17 +0200
| Newsgroups | gmane.comp.lang.eiffel.smalleiffel |
|---|---|
| Organization | Farina Ezio s.r.l. |
| Message-ID | <[email protected]> |
Il giorno lun, 29/05/2006 alle 08.12 +0200, Cyril ADRIAN ha scritto: > Hi Paolo > > On 5/28/06, Paolo Redaelli <[email protected]> wrote: > > Why don't you publish it somewhere, even in the current state, for > > example on gna.org? This way we would be able to avoid duplication of > > efforts.... > > I'll do something of the kind very soon. I just want to be sure that I > have something we can discuss (and that compiles!) Compiling code is the king. Good design is the queen. Handsome performance is their price... 8) > Meanwhile maybe I'll put an article here about the design. > > Paolo who puts his sqlite and postgresql wrappers in hold for a while > > (at least until you answer me 8) > Please don't stop! I'm greedy of backends ;-) Oh no worries... I was just waiting for your email... meanwhile I will go on with these (deferred) classes: DATABASE PREPARED_STATEMENT PREPARED_COMMAND inherit PREPARED_STATEMENT PREPARED_QUERY inherit PREPARED_STATEMENT RESULT_SET [ROW->RESULT_ROW] inherit TRAVERSABLE [ROW] RESULT_ROW inherit TRAVERSABLE [SQL_DATA] SQL_DATA a type yet to be implemented (and perhaps find a really good name); it should be an object that can store any of the datatypes directly handled by SQL: integers, numerics, real, date, time, datetime, strings. I'll have a look at other implementation (i.e.: GnomeDb, ECLI, elj, eiffel PG wrappers http://www.eiffelzone.com/esd/pg/index.html) to avoid design flaws. I hope to be able to commit a proposal by 1st june (I'll be on holiday from 2 to 5)... Paolo