Tom M. wrote:
create_table :foo, :id => false do |t|
I do want a PK, just not autonumber.
Using the method primary_key() makes it autonumber.
I think you’d be better off creating a unique
ID on the research company’s data, in addition
to Rail’s ID, but if you want the extra pain,
go for it.
I certainly agree that ActiveRecord is happiest this way. Let me
describe a bit more the situation, and maybe you’ll see why I want to do
The research consists of huge numbers of files, with huge numbers of
records, referencing eachother through integer FK’s, in text delimited
Using random PK’s makes loading the references a nightmare. The load
procedure needs to do all the work manually. If you make a mistake,
it’s very hard to sort out what happened. Adding new tables (purchased
later) is very hard.
The data is read only under normal operations - all we do is load it -
so I’d rather make the load easy.