Subject | RE: [Firebird-Java] NOT NULL |
---|---|
Author | Robert DiFalco |
Post date | 2003-07-09T17:40:27Z |
Sorry, this was meant for fb-support.
-----Original Message-----
From: Robert DiFalco
Sent: Wednesday, July 09, 2003 9:54 AM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] NOT NULL
Is there any overhead associated with NOT NULL? I ask because all my
inserts and updates are controlled by an application layer -- most
pre-update or pre-insert validation is done there as it is more flexible
for my situation. I know it's a good idea to specify NOT NULL when
appropriate, if for no other reason than to have a self-documenting
schema -- however, I am wondering what the expense of such a constraint
is.
TIA,
Robert
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
-----Original Message-----
From: Robert DiFalco
Sent: Wednesday, July 09, 2003 9:54 AM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] NOT NULL
Is there any overhead associated with NOT NULL? I ask because all my
inserts and updates are controlled by an application layer -- most
pre-update or pre-insert validation is done there as it is more flexible
for my situation. I know it's a good idea to specify NOT NULL when
appropriate, if for no other reason than to have a self-documenting
schema -- however, I am wondering what the expense of such a constraint
is.
TIA,
Robert
Yahoo! Groups Sponsor
To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.