Re: Re: EiffelStore: multiple data stores
aha... A colleague of mine would say: It depends :)
If you are trying to achieve loading data from one, and storing that data in another engine (or backend or
whatever is your preferred term), you could inherit from DATABASE_APPL [MYSQL] in the saver and from
DATABASE_APPL [ODBC] in the loader.
Generally, I would assume that you could inherit from two DATABASE [MYSQL] and DATABASE [ODBC] thingies,
rename *everything* appropriately and call the renamed features. This is mighty shitty ('xcuse my
English) to setup, I agree ;)
Perl's binding interface is much more powerful, due to the fact that the language(!) allows auto loading.
Eiffel is very declarative in that sense, that you will have to tell the compiler where it can expect to find
the classes. If you don't have the MySQL library e.g., you cannot make the produced C code to actually find
it out of the blue... It would be cool, though :-D
Good luck ;)
From: Joachim Baran <joachim.baran@...>
Sent: Thu, April 1, 2010 9:30:06 PM
Subject: [eiffel_software] Re: EiffelStore: multiple data stores
On 1 April 2010 20:22, Joachim Baran <joachim.baran <at> gmail.com> wrote:
> [...] PostgreSQL besides MySQL [...] replaces ODBC with INGRES.