Ooo, ooo! Definitely a MySQL mode. But which of the dozens in
mutually incompatible releases would that be? 5.0.x? 5.1.1? 5.1.y?
5.1.z? And home many of the dozens of incompatible operating modes
would you include in each?

MySQL expects that applications will require porting from x.y.z to
x.y.<z+1>. Ugh. On the other hand, their users have been well
trained. And they have to support and maintain a whole trail of old
releases.

My experience has been that users almost never, ever, port a working
application from database A to database B. Looking at the issue from a
NimbusDB planning perspective, we decided to stick with standard SQL and
extensions of our own choosing on the assumption that we will be used
for new applications doing forward, not old applications going backward.

Do what you think is technically best.

On 9/8/2010 6:32 AM, Dalton Calford wrote:
> Are you suggesting a 'dialect oracle' ? How about a 'dialect mssql'?
>
> The big question is, should the parser be a plugin including some system
> views that support various databases including their information schema?
>
> That would be powerful and allow firebird to be a drop in replacement of
> many database backends.
>
> On 8 September 2010 05:44, marius adrian popa<mapopa@...> wrote:
>
>>
>> what happened to fyracle mode ?
>>
>> http://www.firebirdnews.org/docs/papers/fyracle_wsw.pdf
>>
>> i see some of it's components/features would be integrated in 3.0 (see
>> the roadmap screeshot)
>> it would be nice to have an oracle "mode" for migrations from oracle
>>
>> also it would be nicer to have full pl/sql support too
>>
>>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>


--
Jim Starkey
Founder, NimbusDB, Inc.
978 526-1376