On Sep 22, 2008, at 2:18 PM, Uwe Grauer wrote:
> Please tell us why you would want to have CHAR(3) as your PK.
> I'm asking because i would use technical PKs whenever possible.
> If you need CHAR(3) as a unique key for lookups, just add a CHAR(3)
> field with a unique key constraint in addition to your technical PK of
> type NUMERIC(18,0) which is a BIGINT for Firebird.
I don't believe that the question was one seeking information about
database design.
No matter what the type/size of the PK selected, there should be
*some* way to enable manually entering and saving them, no matter how
wise or unwise that practice may be. I plan on looking into this code
this evening.
-- Ed Leafe
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
Searchable Archives: http://leafe.com/archives/search/dabo-users
This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
