Svein Erling Tysvær wrote:

>German, you say "not unique" for the FKs. Exactly how "not unique" is
>this? It is OK to have a foreign key to customer in the order table,
>but it is not OK to have a foreign key to status when 90% of the
>records have the status 'Completed'.
>

I font have that kind of foreign key (like status) but yes can happen
there the same key in the 90% of records.
Thats is bad? So please explain me how can i manage that in a real life
app. If that key is by example payment, how can i know if the people
will pay with cash or visa before create the table?
I really dont understand why that is a trouble in firebird.Must be
another solution. I dont want to remove foreign keys and lost
referential integrity.

>And what does the three seconds
>include? Connect to database, insert record, commit transaction or
>simply insert record without connection or transaction timing.
>

Start transaction
Insert
Commit Transaction

>Do you
>have any triggers firing at the time of insert (I thought duplicates
>wouldn't cause much trouble when inserting, but that updating and
>deleting could suffer from duplicates)?
>
>
>

Just inserting, not updating, not deleting.

Any other idea?

TIA