From: Glen Holcomb <damnbigman@...>
Date: 2008-06-26T02:57:04+09:00
Subject: Re: Sequel primary keys

------=_Part_35602_20556674.1214416751565
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Wed, Jun 25, 2008 at 11:41 AM, Dave Bass <davebass@musician.org> wrote:

> Glen Holcomb wrote:
> > Does anyone on here know if it is possible to create a non-integer
> > primary
> > key in Sequel?
>
> If you mean a floating-point primary key, that doesn't sound like a good
> idea, for the same reason that doing == comparisons with floats isn't a
> good idea.
> --
> Posted via http://www.ruby-forum.com/.
>
>
No, I was looking to do more what Todd was talking about.  I've never seen
any reason to generate a pointless counter for a key and in analog extra
constraints when the DBMS handles it for you simply by working in sets (and
in some cases bags).  If my DB is a model of real world entities as it
should be then there should be a unique indentifier for said entities which
means I shouldn't have to number them just because.

In other words I am using necessary table elements as keys.

-- 
"Hey brother Christian with your high and mighty errand, Your actions speak
so loud, I can't hear a word you're saying."

-Greg Graffin (Bad Religion)

------=_Part_35602_20556674.1214416751565--