On Thu, Feb 14, 2013 at 4:12 AM, Ruben Marti wrote:
>
> create table PRICES {
> START_DATE date default current_date not null,
> ITEM varchar(10) default '' not null,
> PRICE double precision default 0 not null
> };
> alter table PRICES add constraint PK_PRICES primary key (START_DATE
upport@yahoogroups.com]
En nombre de Helen Borrie
Enviado el: jueves, 14 de febrero de 2013 6:40
Para: firebird-support@yahoogroups.com; firebird-support@yahoogroups.com
Asunto: Re: [firebird-support] Doubt creating index
At 05:48 p.m. 14/02/2013, W O wrote:
>So, Helen, if an index use th
You are right, bad reading, he says "composite primary key", sorry.
Greetings.
Walter.
On Thu, Feb 14, 2013 at 3:13 AM, W O wrote:
> Yes, of course, if column A is a primary key (or part of it) then should
> be not updatable. But for the context I didn't understood it was a PK.
>
> Greetings
Yes, of course, if column A is a primary key (or part of it) then should be
not updatable. But for the context I didn't understood it was a PK.
Greetings.
Walter.
On Thu, Feb 14, 2013 at 1:39 AM, Helen Borrie wrote:
> **
>
>
> At 05:48 p.m. 14/02/2013, W O wrote:
> >So, Helen, if an index u
At 05:48 p.m. 14/02/2013, W O wrote:
>So, Helen, if an index use the column A, then (ideally) the column A should
>not be updatable?
>
>That's new for me.
It is also a wrong take on what I said. "Column A" in this case is a field in
the Primary Key. It is extremely poor design to have PK's tha
So, Helen, if an index use the column A, then (ideally) the column A should
not be updatable?
That's new for me.
Greetings.
Walter.
On Wed, Feb 13, 2013 at 8:28 PM, Helen Borrie wrote:
> **
>
>
> At 12:44 p.m. 14/02/2013, Ruben Marti wrote:
> >I have a table with several hundreds of thous
At 12:44 p.m. 14/02/2013, Ruben Marti wrote:
>I have a table with several hundreds of thousands of records that has a
>composite primary key, with the fields "START_DATE" and "ITEM".
>
>I honestly do not know if it's interesting declare the index as "UNIQUE"
>when it can not have duplicate records
I have a table with several hundreds of thousands of records that has a
composite primary key, with the fields "START_DATE" and "ITEM".
For optimization reasons, I need an index composed of the fields "ITEM" and
"START_DATE".
I honestly do not know if it's interesting declare the index as "UNIQUE
