From: Justin Clift <justin@postgresql.org>
To: Neil Conway <neilc@samurai.com>
Cc: Oliver Elphick <olly@lfix.co.uk>
Cc: Robert Treat <xzilla@users.sourceforge.net>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] Bug with sequence
Date: Thu, 21 Nov 2002 14:46:54 +1100
Message-ID: <3DDC572E.F4B45BC4@postgresql.org> (raw)
References: <92c0776e.0211180745.49911131@posting.google.com>
<1037782392.29678.88.camel@linda>
<1037828113.23925.101.camel@camel>
<1037830378.24840.40.camel@linda>
<3DDC47A9.4C0BC2DE@postgresql.org>
<877kf74mex.fsf@mailbox.samurai.com>
Neil Conway wrote:
>
> Justin Clift <justin@postgresql.org> writes:
> > This sounds like a serious bug in our behaviour, and not something
> > we'd like to release.
>
> It's not ideal, I agree, but I *definately* don't think this is
> grounds for changing the release schedule.
Hey, I'm no fan of slowing the release schedule either.
Bug this is definitely sounding like a bug.
> > No real issue with the nicety for newbies, but am very concerned
> > about the lack of a dependancy check here.
>
> Well, how would you suggest we fix this? ISTM this is partially a
> result of the fact that we don't produce dependancy information for
> function bodies. While it might be possible to do so (in 7.4) for
> certain types of functions (e.g. for functions defined in SQL,
> PL/PgSQL, etc.), I can't see a general solution (e.g. for functions
> defined in C).
Absolutely *no* idea.
> And adding random hacks to get specific functions (e.g. nextval()) to
> work does not strike me as a very good idea.
Agreed. Random hacks aren't always a good approach.
Regards and best wishes,
Justin Clift
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: justin@postgresql.org, neilc@samurai.com, olly@lfix.co.uk, xzilla@users.sourceforge.net, pgsql-hackers@postgresql.org
Subject: Re: [GENERAL] Bug with sequence
In-Reply-To: <3DDC572E.F4B45BC4@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox