Because at this company, the client dictates the DB structure. No matter
how absurd, what the client wants, the client gets here. It's very
strange but what I have to deal with.
Message from Christopher Reed
<[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM received on 10/26/2005
09:13 AM
10/26/2005 09:13 AM
Christopher Reed <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM
Please respond to "Discussion of advanced .NET topics."
<ADVANCED-DOTNET@DISCUSS.DEVELOP.COM>
Sent by "Discussion of advanced .NET topics."
<ADVANCED-DOTNET@DISCUSS.DEVELOP.COM>
To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
cc:
Subject: Re: [ADVANCED-DOTNET] Primary Key Bug
I believe that this occurs when using the VARCHAR2 data type.
I guess I'm confused as to the problem that you're having with this.
In my experience, you should not use a string column for primary keys in
the first place, let alone a column where the values are inserted by
users. Unless I have a compelling reason, I generally use integers for
my primary key values to avoid this type of situation. Overall, using
strings in your primary key is not a best practice, so why do you need
to?
Christopher Reed
Web Applications Supervisor
Information Technology
City of Lubbock
[EMAIL PROTECTED]
"The oxen are slow, but the earth is patient."
>>> [EMAIL PROTECTED] 5:47:59 pm 10/25/2005 >>>
Oracle allows it in it's primary key.
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
===================================
This list is hosted by DevelopMentor® http://www.develop.com
View archives and manage your subscription(s) at http://discuss.develop.com
