Re: [OT] Not everything goes well in Ruby land :-)

> If you expose any "developer private" information, users are going  
> to start to rely on it. Consider it UI. Preventing you from making  
> changes. I.e. Users could start bookmarking URLs with primary keys  
> in them.
But that's perfectly valid, right?  RESTful folks would say that your  
URL's ARE API ... Especially if you start exposing ActiveResource- 
style RESTful XML services, those are going to have to have SOME sort  
of ID's in them.  Like Chuck said, you could use some other candidate  
key, but if you have a sufficient non-OID candidate key that is going  
to be basically invariant and act in this capacity in your API, why  
not just make that your PK in WO in the first place?

ms