Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
On July 5, 2002 10:27 am, Marc G. Fournier wrote:
On Fri, 5 Jul 2002, Tom Lane wrote:
Marc G. Fournier [EMAIL PROTECTED] writes:
Actually, the big change is such that will, at least as far as I'm
understanding it, break pretty much every front-end applicaiton ...
Only those that inspect system catalogs --- I'm not sure what percentage
that is, but surely it's not pretty much every one. psql for example
is only affected because of its \d commands.
Okay, anyone have any ideas of other packages that would inspect the
system catalog? The only ones I could think of, off the top of my head,
would be pgAccess, pgAdmin and phpPgAdmin ... but I would guess that any
'administratively oriented' interface would face similar problems, no?
PyGreSQL pokes into the catalogues a bit.
--
D'Arcy J.M. Cain darcy@{druid|vex}.net | Democracy is three wolves
http://www.druid.net/darcy/| and a sheep voting on
+1 416 425 1212 (DoD#0082)(eNTP) | what's for dinner.
---(end of broadcast)---
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
On Fri, 5 Jul 2002, Curt Sampson wrote: While there are big changes between 7.2 and the next release, they aren't really any bigger than others during the 7.x series. I don't really feel that the next release is worth an 8.0 rather than a 7.3. But this is just an opinion; it's not something I'm prepared to argue about. Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... which, I'm guessing, is pretty major, no? :) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
On Fri, 5 Jul 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... Only those that inspect system catalogs --- I'm not sure what percentage that is, but surely it's not pretty much every one. psql for example is only affected because of its \d commands. Okay, anyone have any ideas of other packages that would inspect the system catalog? The only ones I could think of, off the top of my head, would be pgAccess, pgAdmin and phpPgAdmin ... but I would guess that any 'administratively oriented' interface would face similar problems, no? ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am being interviewed by OReilly )
Marc G. Fournier [EMAIL PROTECTED] writes: Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... Only those that inspect system catalogs --- I'm not sure what percentage that is, but surely it's not pretty much every one. psql for example is only affected because of its \d commands. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... which, I'm guessing, is pretty major, no? :) I've always thought of our release numbering as having themes. The 6.x series took Postgres from interesting but buggy to a solid system, with a clear path to additional capabilities. The 7.x series fleshes out SQL standards compliance and rationalizes the O-R features, as well as adds to robustness and speed with WAL etc. And the 8.x series would enable Postgres to extend to distributed systems etc., quite likely having some fundamental restructuring of the way we handle sources of data (remember our discussions a couple years ago regarding tuple sources?). So I feel that bumping to 8.x just for schemas is not necessary. I *like* the idea of having more than one or two releases in a series, and would be very happy to see a 7.3 released. - Thomas ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
On Fri, 5 Jul 2002, Thomas Lockhart wrote: Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... which, I'm guessing, is pretty major, no? :) I've always thought of our release numbering as having themes. The 6.x series took Postgres from interesting but buggy to a solid system, with a clear path to additional capabilities. The 7.x series fleshes out SQL standards compliance and rationalizes the O-R features, as well as adds to robustness and speed with WAL etc. And the 8.x series would enable Postgres to extend to distributed systems etc., quite likely having some fundamental restructuring of the way we handle sources of data (remember our discussions a couple years ago regarding tuple sources?). So I feel that bumping to 8.x just for schemas is not necessary. I *like* the idea of having more than one or two releases in a series, and would be very happy to see a 7.3 released. Seems I'm the only one for 8.x, so 7.3 it is :) ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
Marc G. Fournier wrote: On Fri, 5 Jul 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Actually, the big change is such that will, at least as far as I'm understanding it, break pretty much every front-end applicaiton ... Only those that inspect system catalogs --- I'm not sure what percentage that is, but surely it's not pretty much every one. psql for example is only affected because of its \d commands. Okay, anyone have any ideas of other packages that would inspect the system catalog? The only ones I could think of, off the top of my head, would be pgAccess, pgAdmin and phpPgAdmin ... but I would guess that any 'administratively oriented' interface would face similar problems, no? That's a good point. Only the admin stuff is affected, not all applications. All applications _can_ now use schemas, but for most cases applications remain working unchanged. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: [HACKERS] Should next release by 8.0 (Was: Re: [GENERAL] I am
In my book, schema support is a big thing, leading to rethink a lot of database organization and such. PostgreSQL 8 would stress this importance. -- Alessio F. Bragadini[EMAIL PROTECTED] APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-22-755750 It is more complicated than you think -- The Eighth Networking Truth from RFC 1925 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
