Re: Postgres 9.1 - Release Theme

"Following a great deal of discussion, I'm pleased to announce that the
PostgreSQL Core team has decided that the major theme for the 9.1
release, due in 2011, will be 'NoSQL'.

"... the intention is to remove SQL support from
Postgres, and replace it with a language called 'QUEL'. This will
provide us with the flexibility we need to implement the features of
modern NoSQL databases. With no SQL support there will obviously be
some differences in the query syntax that must be used to access your
data. "

hmm.. shock it is ....this shift for 9.1 due in mid 2011 is unexpectedly
soon :)

Curious to understand as to

- how this relates to every feature that is provide at the moment based on
RDBMS paradigm.

ACID compliance, support for the features provided by SQL, referential
integrity, joins, caching etc, ..

- Also does this shift take into an assumption that all the use cases fit
the likes of data access patterns & usecases similar to facebook/twitter?
or to address the the likes of those ?

Thanks,
Raj

Smells like April first to me.
http://en.wikipedia.org/wiki/April_Fools'_Day

From: pgsql-general-owner(at)postgresql(dot)org [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Rajasekhar Yakkali
Sent: Friday, April 01, 2011 10:08 AM
To: dpage(at)postgresql(dot)org
Cc: pgsql-general(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] Postgres 9.1 - Release Theme

"Following a great deal of discussion, I'm pleased to announce that the
PostgreSQL Core team has decided that the major theme for the 9.1
release, due in 2011, will be 'NoSQL'.

"... the intention is to remove SQL support from
Postgres, and replace it with a language called 'QUEL'. This will
provide us with the flexibility we need to implement the features of
modern NoSQL databases. With no SQL support there will obviously be
some differences in the query syntax that must be used to access your
data. "

hmm.. shock it is ....this shift for 9.1 due in mid 2011 is unexpectedly soon :)

Curious to understand as to

- how this relates to every feature that is provide at the moment based on RDBMS paradigm.

ACID compliance, support for the features provided by SQL, referential integrity, joins, caching etc, ..

- Also does this shift take into an assumption that all the use cases fit the likes of data access patterns & usecases similar to facebook/twitter? or to address the the likes of those ?

Thanks,
Raj

On 4/1/11 11:34 AM, Dann Corbit wrote:
> Smells like April first to me.
> http://en.wikipedia.org/wiki/April_Fools'_Day

Actually, someone recycled Dave's April 1 announcement from last year.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

I was under the impression that QUEL was actually a good language in some ways,
and that it was more relational and better than SQL in some ways.

http://en.wikipedia.org/wiki/QUEL_query_languages

Maybe bringing it back would be a good idea, but as an alternative to SQL rather
than a replacement.

In any event, QUEL was somewhat similar to SQL.

-- Darren Duncan

Rajasekhar Yakkali wrote:
> "Following a great deal of discussion, I'm pleased to announce that the
> PostgreSQL Core team has decided that the major theme for the 9.1
> release, due in 2011, will be 'NoSQL'.
>
> "... the intention is to remove SQL support from
> Postgres, and replace it with a language called 'QUEL'. This will
> provide us with the flexibility we need to implement the features of
> modern NoSQL databases. With no SQL support there will obviously be
> some differences in the query syntax that must be used to access your
> data. "
>
> hmm.. shock it is ....this shift for 9.1 due in mid 2011 is unexpectedly
> soon :)
>
> Curious to understand as to
>
> - how this relates to every feature that is provide at the moment based on
> RDBMS paradigm.
>
> ACID compliance, support for the features provided by SQL, referential
> integrity, joins, caching etc, ..
>
> - Also does this shift take into an assumption that all the use cases fit
> the likes of data access patterns & usecases similar to facebook/twitter?
> or to address the the likes of those ?
>
> Thanks,
> Raj
>