Summary
For some reason right after I save a model to the db, the id says
‘0’…yet next transaction the db properly has it listed as the correct
id.
Details:
I have a SQLite3 DB with the following schema:
CREATE TABLE projects (
id INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL,
address TEXT NOT NULL,
created_on INTEGER,
updated_on INTEGER
);
I have a corresponding Project model.
In one of my controllers, I have the following code:
project = Project.new
project.address = @params[ ‘address’ ]
if project.save
p “Assigning id: #{project.id}!!!”
# …stuff that relies on the id being correct…
end
When I run that controller/view, I see “Assigning id: 0!!!” in the
output.
When I then do a Project.find_all, or query the DB directly, it
properly has an id of 1.
This occurs for all projects created by that view (not just the first).
The id 0 problem occurs not just using project.save directly in a
controller, but also when using the after_create or after_save
callbacks inside the model.
Is this a known problem with SQLite3? Do I need to bite the bullet and
let rails tell me what kind of DB to use?
Or is this a misunderstanding on my part? Is there something else I
need to do to get the actual ID of the row that I’ve just created? (My
desire is to then create a bunch of other models as defaults that are
associated in a has_many relationship with the Project.)