Autoincrement keys using DataMapper with legacy PostgreSQL db?

You can use the nextval() function in an expression to fetch and use the next sequence value as the id : INSERT INTO "production". "companies" ("name", "id") VALUES ('Acme Inc. ', nextval('production.

Sequence_id_seq') ) I don't know enough about DataMapper to say whether or not it's possible to cause a function to be used in an INSERT, but maybe there's some way to do it by defining your own Datamapper::Property (instead of Serial)? Alternatively, you could alter the table to make the row default to using the sequence, which shouldn't break compatibility with anything that manually uses the same sequence: ALTER TABLE production. Companies ALTER COLUMN id SET DEFAULT nextval('production.

Sequence_id_seq').

You can use the nextval() function in an expression to fetch and use the next sequence value as the id: INSERT INTO "production". "companies" ("name", "id") VALUES ('Acme Inc. ', nextval('production.

Sequence_id_seq') ) I don't know enough about DataMapper to say whether or not it's possible to cause a function to be used in an INSERT, but maybe there's some way to do it by defining your own Datamapper::Property (instead of Serial)? Alternatively, you could alter the table to make the row default to using the sequence, which shouldn't break compatibility with anything that manually uses the same sequence: ALTER TABLE production. Companies ALTER COLUMN id SET DEFAULT nextval('production.

Sequence_id_seq').

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.