> -----Original Message-----
> From: Ann Harrison [mailto:harrison@...]
> Sent: Miércoles 6 de Septiembre de 2000 12:25
>
> At 09:45 PM 9/5/00 -0400, Claudio Valderrama C. wrote:
>
> >We only handle here conversions from WhateverElse to Interbase, not the
> >opposite.
>
> Claudio, that's parochial of you, though I agree that the list at
> mers.com would be a better place to ask that question.

Parochial, did you say Parochial, Mom? Well, let's see the list charter:
<g>
«
IB-Conversions
Founded June 18, 2000
Description
List for documenting the issues of converting other DBMS to InterBase.
»

Now, seriously speaking: I'm not chauvinist. I've stated several times in
the NGs that one should use the DBMS that best fits the task to be done. IB
is not my only engine, of course. While I understand the legitimate need or
concern on how to "escape from IB", the primary aim of the list is to help
newcomers to migrate TO interbase and to use the possible discussions here
to document general migration issues.
I'm not going to bash occasional people asking for the opposite, tho. If
anybody knows the answer, that's ok. Also, given a doc that describes how to
go from XYZ to IB, it should be possible to read it "in reverse" to have a
basic understanding on how to go from IB to XYZ. Unfortunately, we don't
have yet an Oracle to IB basic guide.

> Yes, an InterBase application can be converted to Oracle. The
> ease (or difficulty) will come primarily from triggers and stored
> procedures. Oracle has both, but their implementation is not at
> all the same.

Also, since IB has less built-in functions, going to Oracle should be less
pain that going from Oracle, at least in SQL statements. What I ignore is
whether Oracle provides some equivalent of selectable stored procedures.
Rob Schieck's MERS is a partner of both IB and Oracle. He could give more
information in his
mers.interbase.list IMHO.

C.