Re: On the right tool (was Re: [GENERAL] Proper relational database?)

2016-04-23 Thread david
> ow...@postgresql.org] On Behalf Of Andrew Sullivan > Indeed, I wasn't trying to make some point-and-laugh argument about NoSQL. I > was just observing that, as with many new techniques, some of the uses > haven't really been thought out carefully. (It doesn't help that at least > one of the ea

On the right tool (was Re: [GENERAL] Proper relational database?)

2016-04-23 Thread Andrew Sullivan
Hi, On Sun, Apr 24, 2016 at 12:55:48PM +1000, da...@andl.org wrote: > But there is goodness there, and NoSQL is now just as hard to replace. Indeed, I wasn't trying to make some point-and-laugh argument about NoSQL. I was just observing that, as with many new techniques, some of the uses haven't

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
> ow...@postgresql.org] On Behalf Of Eric Schwarzenbach > >> If I had a few $million to spend in a philanthropical manner, I would > >> hire some of the best PG devs to develop a proper relational database > server. > >> Probably a query language that expressed the relational algebra in a > >> sch

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
> From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general- > This turns out to be true in many areas of language design, mutli-user system > security, virtually everything to do with networking, and application > deployment. I was at an IETF meeting some years ago where someone talking >

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
From: pgsql-general-ow...@postgresql.org [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Guyren Howe Why schema-on-demand? Can you explain what you mean by that? Something that is attractive, for beginners or perhaps when prototyping is that you don't have to declare a table. You c

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
Absolutely not. SQL is a (nearly) full implementation of the relational algebra, plus other non-relational stuff. The only thing it really can't handle is a table with no columns! (I have to fake that) a table with no columns would have no primary key... doesn't that violate one of the fundame

Re: [GENERAL] Is it possible to recover the schema from the raw files?

2016-04-23 Thread Venkata Balaji N
On Sun, Apr 24, 2016 at 2:30 AM, Tomas J Stehlik wrote: > Hello, > > There was a corruption to the file system due to sudden shutdown of Windows > 7. > > The attempt to connect to one of the databases results in multiple errors, > like the following one: > ERROR: invalid page in block 58 of rela

Re: [GENERAL] Proper relational database?

2016-04-23 Thread Andrew Sullivan
On Thu, Apr 21, 2016 at 01:36:54PM -0700, Guyren Howe wrote: > It's an enormous tragedy that all the development effort that has > gone into NoSQL database has pretty much all gotten it wrong: by all > means throw out SQL, but not the relational model with it. They're > all just rehashing the deb

[GENERAL] Is it possible to recover the schema from the raw files?

2016-04-23 Thread Tomas J Stehlik
Hello, There was a corruption to the file system due to sudden shutdown of Windows 7. The attempt to connect to one of the databases results in multiple errors, like the following one: ERROR: invalid page in block 58 of relation base/161326/233745 Several raw files were completely lost (zeroed)

Re: [GENERAL] Proper relational database?

2016-04-23 Thread Manuel Gómez
On Sat, Apr 23, 2016 at 10:39 AM, Geoff Winkless wrote: > SELECT with no values is selecting a NULL, and two NULLs do not > equate, so you would expect two rows. This is precisely what I mean by wonky semantics: it makes no sense for a nullary relation to be interpreted as selecting a NULL. A ro

Re: [GENERAL] Proper relational database?

2016-04-23 Thread Joshua D. Drake
On 04/23/2016 08:09 AM, Geoff Winkless wrote: On 23 April 2016 at 07:08, Manuel Gómez wrote: but its semantics can be rather wonky. Witness: postgres=# select 1; ?column? -- 1 (1 row) postgres=# select 1 union select 1; ?column? -- 1 (1 row) Exactly w

Re: [GENERAL] Proper relational database?

2016-04-23 Thread Geoff Winkless
On 23 April 2016 at 07:08, Manuel Gómez wrote: > but its semantics can be rather wonky. Witness: > > postgres=# select 1; > ?column? > -- > 1 > (1 row) > > postgres=# select 1 union select 1; > ?column? > -- > 1 > (1 row) Exactly what you would expect. Use UNIO

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
> From: Thomas Munro [mailto:thomas.mu...@enterprisedb.com] > FWIW standard SQL may not allow it but Postgres does, and it's even possible > to exclude duplicates by using an expression that references the whole row. Thank you. I didn't know that. I'll use it if I can verify it works right. It'

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
> This is a relevant project: https://github.com/agentm/project-m36 Thanks -- I didn't know about that one. I'll add it to my list. It's quite unlike other implementations. I have some reading to do. Regards David M Bennett FACS Andl - A New Database Language - andl.org -- Sent via pgsq

Re: [GENERAL] Proper relational database?

2016-04-23 Thread david
> ow...@postgresql.org] On Behalf Of Guyren Howe > Sent: Saturday, 23 April 2016 4:04 AM > To: Raymond Brinzer > Subject: Re: [GENERAL] Proper relational database? > > On Apr 22, 2016, at 10:45 , Raymond Brinzer wrote: > The fundamental storage model needs to at least be a bit different. In > p

Re: [GENERAL] Add relcreated (timestamp) column to pg_class catalog to record the time an object was created

2016-04-23 Thread Melvin Davidson
On Sat, Apr 23, 2016 at 1:03 AM, Shulgin, Oleksandr < oleksandr.shul...@zalando.de> wrote: > On Apr 22, 2016 19:46, "Melvin Davidson" wrote: > > > > > > First, tahnk you for your feedback Alex. > > > > "IMO, every time it was conclusively demonstrated that when you consider > dump/restore semanti

Re: [GENERAL] Proper relational database?

2016-04-23 Thread Kevin Grittner
On Sat, Apr 23, 2016 at 1:53 AM, Guyren Howe wrote: > On Apr 22, 2016, at 18:56 , wrote: > Why schema-on-demand? Can you explain what you mean by that? > > Something that is attractive, for beginners or perhaps when prototyping is > that you don't have to declare a table. You can just insert tu