Re: Is Ingres yet relational?

From: Paul Mason <Paul_member_at_newsguy.com>
Date: 27 May 2004 02:30:16 -0700
Message-ID: <c94cf801phh_at_drn.newsguy.com>


In article <pan.2004.05.26.15.20.48.49473_at_dutra.fastmail.fm>, Leandro Guimaraens Faria Corsetti Dutra says...
>
>Em Wed, 26 May 2004 07:06:27 -0700, Paul Mason escreveu:
>
>>> I wonder if such a QUEL-only applications would avoid
>>>duplicates, NULLs and the such.
>>
>> If you specifically wrote your application that way it would. NULLs and
>> duplicates exist but you're not forced to use them.
>
> Indeed, but their existence, and that of SQL access,
>inherently hinders optimisation.
>

I don't know enough about the internal architecture to know if that statement is true or not.

>
>>Depends what you mean. You can run Ingres, write applications for it and never
>> have to type an SQL command - however some tools will use SQL themselves.
>>You can also run QUEL queries against views defined in SQL - so you do not need
>>to rely on SQL to query the system catalogs (many of which are still defined in
>> QUEL)
>
> Better than nothing...
>
> Actually what I was thinking was the possibility of creating a
>'relational Ingres' by striping it of SQL, perhaps replacing it by
>Alphora's RealSQL. But perhaps it would be just as easy to backport
>QUEL to PostgreSQL...
>

It might even be easier to start with 'university Ingres' (which is QUEL only) and try to enhance it using the current Ingres source as a guide. Or it might not ;)

Whichever route you choose I think it will be a significant amount of work. Received on Thu May 27 2004 - 11:30:16 CEST

Original text of this message