Subject | RE: [firebird-support] Re: Non null column, before insert trigger not filling column, Delphi |
---|---|
Author | Dunbar, Norman |
Post date | 2010-06-16T14:57:25Z |
Hi Martijn,
Back at the start of the thread I mentioned to Mike that if I created a
table as follows:
create table whatever (
id integer primary key,
...);
Then even though I didn't specify it, the ID column would be changed to
NOT NULL. I have no problem with this happening, I understand that a PK
column needs to be NOT NULL, and Oracle, which I work with does exactly
the same.
My problem was/is that if I try the following:
create table whatever (
id integer,
...);
alter table whatever add constraint pk_whatever
primary key (id)
using index some_index;
Then an error occurs. The ID column is not changed to NOT NULL silently,
and the command fails.
Mike, on the other hand, *is* able to run the above command quite
happily without getting an error. We are both using exactly the same
version of Firebird - 2.1.3.
Cheers,
Norman.
Norman Dunbar
Contract Senior Oracle DBA
CIS Engineering Services
Internal : 7 28 2051
External : 0113 231 2051
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
>> If you create the PK as part of the CREATE TABLE statement, then yes,Yes, I've tested that already and it is indeed true.
>> it will be set to "not null" automagically.
Back at the start of the thread I mentioned to Mike that if I created a
table as follows:
create table whatever (
id integer primary key,
...);
Then even though I didn't specify it, the ID column would be changed to
NOT NULL. I have no problem with this happening, I understand that a PK
column needs to be NOT NULL, and Oracle, which I work with does exactly
the same.
My problem was/is that if I try the following:
create table whatever (
id integer,
...);
alter table whatever add constraint pk_whatever
primary key (id)
using index some_index;
Then an error occurs. The ID column is not changed to NOT NULL silently,
and the command fails.
Mike, on the other hand, *is* able to run the above command quite
happily without getting an error. We are both using exactly the same
version of Firebird - 2.1.3.
Cheers,
Norman.
Norman Dunbar
Contract Senior Oracle DBA
CIS Engineering Services
Internal : 7 28 2051
External : 0113 231 2051
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else. We have checked this email and its attachments for viruses. But you should still check any attachment before opening it. We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes. If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk
Information in this message may be confidential and may be legally privileged. If you have received this message by mistake, please notify the sender immediately, delete it and do not copy it to anyone else.
We have checked this email and its attachments for viruses. But you should still check any attachment before opening it.
We may have to make this message and any reply to it public if asked to under the Freedom of Information Act, Data Protection Act or for litigation. Email messages and attachments sent to or from any Environment Agency address may also be accessed by someone other than the sender or recipient, for business purposes.
If we have sent you information and you wish to use it please read our terms and conditions which you can get by calling us on 08708 506 506. Find out more about the Environment Agency at www.environment-agency.gov.uk