Gerry Snyder wrote:
> I am not sure what all this means when taken together.
>
> It sounds as if defining id as shown above is unnecessary, since it is
> just an alias for ROWID, and if one is stable the other has to be. Correct?
>
> So now I can't interpret "ROWID can change" as meaning
D. Richard Hipp wrote:
> On Sep 6, 2008, at 2:50 AM, Scott Hess wrote:
>
>
>> On Fri, Sep 5, 2008 at 11:31 PM, jonwood <[EMAIL PROTECTED]>
>> wrote:
>>
>>> But the documentation states the ROWID
>>> can change at any time so I'm not sure what I can do safely.
>>>
>> Do this:
On Sat, Sep 6, 2008 at 7:44 AM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> On Sep 6, 2008, at 2:50 AM, Scott Hess wrote:
>> As a bonus, if the implementation of SQLite changes, SQL itself won't,
>> so id will _still_ be a valid integer primary key, even if the
>> implementation detail of rowid
On Sat, Sep 6, 2008 at 10:44 AM, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> > As a bonus, if the implementation of SQLite changes, SQL itself won't,
> > so id will _still_ be a valid integer primary key, even if the
> > implementation detail of rowid changes.
>
> I promise that INTEGER PRIMARY
On Sep 6, 2008, at 2:50 AM, Scott Hess wrote:
> On Fri, Sep 5, 2008 at 11:31 PM, jonwood <[EMAIL PROTECTED]>
> wrote:
>> I have a table where the primary key consists of two columns. I'm
>> doing this
>> because these two columns combined must be unique, while each
>> column is not
>>
Scott Hess wrote:
>
> CREATE TABLE t (
> id INTEGER PRIMARY KEY,
> a TEXT NOT NULL,
> b INTEGER NOT NULL,
> UNIQUE (a, b)
> );
>
> (a,b) will be just as unique as in the first case, but now you can use
> id as a stable alias for rowid. There will be the same number of
> btrees (one
On Fri, Sep 5, 2008 at 11:31 PM, jonwood <[EMAIL PROTECTED]> wrote:
> I have a table where the primary key consists of two columns. I'm doing this
> because these two columns combined must be unique, while each column is not
> unique on its own.
>
> Because of the increased complexity of a
I have a table where the primary key consists of two columns. I'm doing this
because these two columns combined must be unique, while each column is not
unique on its own.
Because of the increased complexity of a dual-column primary key for some
operations, I'd like to use ROWID. But the
8 matches
Mail list logo
