Several tables do not have a primary key...indirectly causes problems with PostgreSQL in Rails 2.3
|Resolution:||Wont fix||Affected version:||1.3.1|
There are four tables that do not have a primary key defined in redmine:
This is technically not illegal, but some argue this is not good practice for apps using AR.
My problem is that this exposes what I think is a latent bug in ActiveRecord's postgres adapter in Rails 2.3.14, whereby it can't insert new records in these tables using a generic ActiveRecord:Base class model.
PG environment: 9.1.3 with latest db gem, i.e. pg-0.13.2 for x86.
I am using a generic rails database transfer script to move redmine from a mysql database across to postgres. It fails on these tables. The error message shows that the INSERT statement that AR constructs is putting the clause RETURNING ("ID") onto the INSERT statement, but because there is no column called ID, the insert fails. I have raised a bug report 5562 on (github) rails for this.
Here is the clip of code that does the transfer:
# Now, write out the prod data to the dev db DevelopmentModelClass.transaction do models.each do |model| new_model = DevelopmentModelClass.new(model.attributes) if (model.attributes.has_key?('id')) new_model.id = model.id end new_model.save(false) end
Even though this problem is technically not a defect in redmine itself, because it looks like we're going to be stuck with rails 2.3 for a while yet, I think this problem needs to be worked around by adding the primary keys. I don't see any harm in it, it's good practice anyway, and it's not a postgres-specific change in terms of redmine db schema.
I have attached a rake db:migrate script to add the missing primary keys.
It also makes it possible to use the very useful "convert" rake script (see attached). Run as db:convert:prod2dev to transfer production to development database, crossing db types in the process. The script was originally written my Rama McIntosh but refined a little by me. (Converting redmine exposed a couple of issues not catered for by the original script).
#1 Updated by Jean-Philippe Lang over 7 years ago
- Status changed from New to Closed
- Resolution set to Wont fix
There's no models behind these tables, these are HABTM association tables. They're not supposed to have a primary key.
#2 Updated by Milton Taylor over 7 years ago
I accept that the AR modelling paradigm may be not demand it. For me it's purely a pragmatic device just to get the db transfer done. Until whatever this bug in AR-postgres is fixed, the addition of the ID columns appears to be necessary for the purposes of doing the db transfer, after which it can be rolled back off the target. It really does make this type of transfer a lot easier to be able to use a generic script. Unless anyone has any other ideas on this.
#3 Updated by Jean-Philippe Lang over 7 years ago
Milton Taylor wrote:
I accept that the AR modelling paradigm may be not demand it.
No, this is a requirement. Quoting the Rails guides:
This table should be created without a primary key [...] That’s required for the association to work properly. If you observe any strange behavior in a has_and_belongs_to_many association like mangled models IDs, or exceptions about conflicting IDs chances are you forgot that bit.
#4 Updated by Milton Taylor over 7 years ago
Cool, thanks for the pointers. Interestingly, the fault in the native pg adapter that was giving me the problem referred to above does not seem to exist in the corresponding AR jdbc adapter, but the latter seems to be seriously broken in other respects as I think you have already found. Am presently trying to shine some light on this.
#13 Updated by Milton Taylor over 7 years ago
- File convert.rake added
Just as a postscript for this issue, I have further altered the database transfer script to work around the original obstacle I encountered with transferring the HABTM tables. I have used this script to successfully move all redmine data from a mysql database to a postgresql database. It doesn't matter what version of redmine database you do this on - the script is introspective of the db, i.e. it does not use specific lists of tables nor does it rely on redmine application models. The only requirement is that the two schemas are both at the same rails migration level. As with all these things, make good backups first, and use at your own risk. YMMV.
This rake script really belongs in the wiki somewhere...perhaps one of the dev team might care to create a page for database migration (as in from one db type to another), discussing the various ways this can be accomplished.