Philip Warner <[EMAIL PROTECTED]> writes:
> This would be something I'd like to do as a learning exercise. However,
> aren't we 2 days from beta? Is this enough time to learn how to add a
> function to the backend?
In practice, you've probably got a week. I believe Marc is planning to
be out of
At 11:17 28/09/00 -0400, Tom Lane wrote:
>
>Hmm, good point. There isn't any real easy way to refer to a sequence
>by OID --- the sequence functions only accept names --- but I suppose
>someone out there might be doing something with sequence OIDs.
So long as the backend & metadata don't rely on
Philip Warner <[EMAIL PROTECTED]> writes:
> At 11:01 28/09/00 -0400, Tom Lane wrote:
>> A data-only reload
>> would fail to make that guarantee unless you drop and recreate
>> the sequence.
> Will this cause problems in an existing database because the sequence OID
> changes?
Hmm, good point. T
At 11:01 28/09/00 -0400, Tom Lane wrote:
>A data-only reload
>would fail to make that guarantee unless you drop and recreate
>the sequence.
Will this cause problems in an existing database because the sequence OID
changes?
Philip
Philip Warner <[EMAIL PROTECTED]> writes:
> OK. Given the discussion of 'select nextval', do you know if 'select
> setval' will set the is_called flag?
Looks like it does, both by experiment and by reading the code.
So if you issue a setval() you don't need a nextval() as well.
However you still
At 10:36 28/09/00 -0400, Tom Lane wrote:
>Philip Warner <[EMAIL PROTECTED]> writes:
>> My inclinations is do do the following:
>
>> - Issue 'CREATE SEQUENCE...Initial Value 1...' in OID order
>> - Issue 'SELECT SETVAL...' at end of data load.
>
>Seems reasonable, except you should not necessarily
Philip Warner <[EMAIL PROTECTED]> writes:
> My inclinations is do do the following:
> - Issue 'CREATE SEQUENCE...Initial Value 1...' in OID order
> - Issue 'SELECT SETVAL...' at end of data load.
> This means that a schema-only restore will hgave all sequences set up with
> initial value = 1, an
