Re: Hardcoding database primary key in switch statement / Design, Dependency issue
- From: "Mark Wilden" <mwilden@xxxxxxxxxxxxxxxx>
- Date: Fri, 13 Jul 2007 10:14:48 -0700
I like Nicholas's idea. However, a simpler approach is the one we use, where
tables like ErrorCheck have a Moniker column with a check constraint and a
uniqueness constraint. We refer to rows via the moniker, not the ID.
///ark
.
- Follow-Ups:
- References:
- Prev by Date: AccessViolationException when using Sybase ASE ADO.NET connector to fill DataSet
- Next by Date: Re: DataGridView column order?
- Previous by thread: Re: Hardcoding database primary key in switch statement / Design, Dependency issue
- Next by thread: Re: Hardcoding database primary key in switch statement / Design, Dependency issue
- Index(es):