Joachim Baran | 1 Apr 12:19 2010
Picon

Documentation down?

Hello,

When I pick a library from the left-hand side menu on
http://eiffel.com/libraries/, for example EiffelThread, EiffelWeb or
Eiffel2Java, and then click on 'Documentation' or 'Library API', I get
a 'Page not found'.

Something must have changed recently, since I remember that I used to
read the documentation on those pages earlier on.

Thanks,
Joachim

--

-- 
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

------------------------------------

Jocelyn Fiat [ES] | 1 Apr 14:28 2010

Re: Documentation down?

It seems to be obsolete links

please have a look at
http://docs.eiffel.com/book/solutions/solutions

http://docs.eiffel.com/book/solutions/eiffelthread
http://docs.eiffel.com/book/solutions/eiffelweb
and so on

However, the links will now be redirected to the right url

-- Jocelyn

On Thu, Apr 1, 2010 at 12:19 PM, Joachim Baran <joachim.baran@...>wrote:

> Hello,
>
> When I pick a library from the left-hand side menu on
> http://eiffel.com/libraries/, for example EiffelThread, EiffelWeb or
> Eiffel2Java, and then click on 'Documentation' or 'Library API', I get
> a 'Page not found'.
>
> Something must have changed recently, since I remember that I used to
> read the documentation on those pages earlier on.
>
> Thanks,
> Joachim
>
> --
> B.1079 Michael Smith Building
(Continue reading)

Joachim Baran | 1 Apr 21:22 2010
Picon

EiffelStore: multiple data stores

Hello,

Is there an elegant way to support multiple data stores within a
single Eiffel program?

Right now, I will write something along the lines of:
  DATABASE_APPL [ODBC]
If I decide to support PostgreSQL besides MySQL in my program, then I
would have to include another instance of DATABASE_APPL in my program
that explicitly replaces ODBC with INGRES.

For example, with Perl's DBI it is sufficient to state the used
storage system as a string, which permits programs to cater for
database systems that the developer is not even aware of. Is is
possible to take a similar approach with EiffelStore?

Thanks,
Joachim

--

-- 
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

------------------------------------

(Continue reading)

Joachim Baran | 1 Apr 21:30 2010
Picon

Re: EiffelStore: multiple data stores

Hello, again,

On 1 April 2010 20:22, Joachim Baran <joachim.baran@...> wrote:
> [...] PostgreSQL besides MySQL [...] replaces ODBC with INGRES.
Oh my.. Ingres /= PostgreSQL.

I imagine I will have to use the ODBC driver for PostgreSQL then as well.

Joachim

--

-- 
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

------------------------------------

Guus Leeuw | 1 Apr 22:34 2010
Picon

Re: Re: EiffelStore: multiple data stores

Joachim,

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 ;)
Guus

________________________________
From: Joachim Baran <joachim.baran@...>
To: eiffel_software@...
Sent: Thu, April 1, 2010 9:30:06 PM
Subject: [eiffel_software] Re: EiffelStore: multiple data stores

  
Hello, again,

On 1 April 2010 20:22, Joachim Baran <joachim.baran <at>  gmail.com> wrote:
> [...] PostgreSQL besides MySQL [...] replaces ODBC with INGRES.
(Continue reading)

Guus Leeuw | 1 Apr 22:35 2010
Picon

Announcing EiffelStore MySQL Binding

Please see http://eiffelstudio.origo.ethz.ch/node/385 for the details. Patches are there also.

Regards,
Guus

[Non-text portions of this message have been removed]

------------------------------------

Guus Leeuw | 1 Apr 22:24 2010
Picon

Re: Web and MySQL

Right, I've gone and done the thing and announced MySQL binding available on http://eiffelstudio.origo.ethz.ch/node/385
The patches are there too.

Have fun.

Regards,
Guus

________________________________
From: Guus Leeuw <guusleeuw@...>
To: eiffel_software@...
Sent: Wed, March 31, 2010 11:16:43 PM
Subject: Re: [eiffel_software] Web and MySQL

  
The esql seems to be cool too.
The converter has a problem as far as the keyword_h_table feature from METALEX is concerned. Mailed Manu separately.

____________ _________ _________ __
From: Guus Leeuw <guusleeuw <at> yahoo. com>
To: eiffel_software <at>  yahoogroups. com
Sent: Wed, March 31, 2010 10:52:58 PM
Subject: Re: [eiffel_software] Web and MySQL

  
Hello,

the examples/store/ rm2oom also works now, and I fixed a flaw in the MySQL stub for matching data types, so
that's cool too.

(Continue reading)

Joachim Baran | 1 Apr 23:34 2010
Picon

Re: Re: EiffelStore: multiple data stores

Hello,

On 1 April 2010 21:34, Guus Leeuw <guusleeuw@...> wrote:
> 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.
Good point.

Thanks,
Joachim

--
B.1079 Michael Smith Building
Faculty of Life Sciences
The University of Manchester
Oxford Road
Manchester
M13 9PT
United Kingdom

------------------------------------

David Le Bansais | 1 Apr 23:35 2010
Picon

Re: EiffelStore: multiple data stores


>
> 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 ;)
>

I believe you can't inherit from both GENERIC[G] and GENERIC[H]. I'm not sure if that's a theoretical or
implementation issue though.

Regards,
David Le Bansais

------------------------------------

Martin Piskernig | 1 Apr 23:50 2010
Picon
Picon

Re: Re: EiffelStore: multiple data stores

Am Donnerstag, 1. April 2010 23:35:38 schrieben Sie:
> > 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 ;)
> 
> I believe you can't inherit from both GENERIC[G] and GENERIC[H]. I'm not
>  sure if that's a theoretical or implementation issue though.

It's regulated by 8.6.13 (validity rule VHPR), clause 5.

Regards,
Martin

------------------------------------


Gmane