similar to: validating composite model keys

Due to the foolish implied assumption that there''d never be a revision to activerecord library, the Composite Primary Key code promptly broke for anyone who updated their apps to Rails 1.1.6 (with its activerecord-1.14.4) Now the gem dependencies are fixed and your legacy databases are free to wield composite primary keys without fear again. Description: Composite Primary Keys

Announcement: Composite Primary Keys gem now includes support for ActiveRecord Associations. Summary: Composite Primary Keys allows an ActiveRecord to support 2+ primary keys using the set_primary_keys class method. Previous versions provided full CRUD and find support. This latest release provides support for more ActiveRecord magic: associations (has_many, belongs_to, etc) Full report:

Composite Primary Keys for ActiveRecords Bug fix release - 0.3.3 Notes: Fixed errors with id= and create. Note, the create method does not use sequences to generate ids for you. If anyone has any use cases where their DBs generate ids for their composite keys, pls let me know - we may need to add some syntax to the set_primary_keys command. Url: http://compositekeys.rubyforge.org Summary:

Have been looking into using rails but am finding the "Composite Primary Keys are Bad" thing a tad disturbing (to put it mildly). I have been working with RDBMS systems for over fifteen years and this is the first time I have herd the idea questioned. I have cone across using surrogate keys which mirror the composite key for performance reasons in VERY big databases but I have never

Hello, Is it true that Rails doesn''t support composite primary keys? I have a legacy system and was pondering adding a new interface to it. This whole Rails thing (and yes, Ruby too) seems pretty interesting but I''d feel ashamed of myself adding an additional column called ''id'' when there''s already a perfectly good composite key. Assuming the rumors

ActiveRecords with composite primary keys now seem to happily support find/create/update/destroy options. Url: http://compositekeys.rubyforge.org Background: Rails/ActiveRecords has long been critised for not supporting legacy databases, especially composite primary keys. This gem extends ARs with this support. Cheers Nic -- Posted via http://www.ruby-forum.com/.

I am building an app with existing controllers/actions, using traditional rails routes. I recently started moving over to RESTful routes and have hit a snag. Now I am reconsidering my whole effort and may go back to the original, more flexible, map.connect method. My problem is, one of the resources has composite keys. The keys are both strings as well, and can include dots. Here''s

I know ActiveRecord doesn''t support composite primary keys, but I need to use one, and I need it ASAP. I don''t need any composite foreign keys, luckily; what I have is a table that stores old versions of rows in another table, so the composite key is an id + date stamp. Would someone tell me a hack I can use to support this? -- View this message in context:

hello, what is the strategy you use for composite primary keys ? I saw the solution proposed by Graham Glass ( ticket 3201) using a set_composite_key..., but it seems it is not in AR ....(why ?) thanks for feedback arnaud

I''ve got a user object which has quite a few attributes mapped to the database. As of right now I''ve got some validations in the model like: validates_presence_of :password, :message => "You must specify a valid password." validates_confirmation_of :password, :message => "Password doesn''t match the confirmation." validates_presence_of

I have a legacy db with the following simplified structure: Table-A: type_key, code_key, name, ... # PKs are type_key and code_key, there is no id col and I cannot alter this db Table-B: # each row has only the code as a foreign_key, the type_key is hard-coded to "FOOKEY" an_id, code, ... Models: class TableB < AR::Base set_table_name ''table_b''

i have two table, comment and post, both have composite keys, and no id column, comment belongs to post, i follow the instruction of http://compositekeys.rubyforge.org/, and it seems successfully, (But i still cant confirm to put require ''rubygems'' and require ''composite_primary_keys'' on which file ). I can do the CRUD operation for post,then i want to create

Hi all, I''m using ruby 1.8.2-15 and a recent rails 1.0 download. I''m trying to implement the Classic/Custom pagination in a list action. Here''s my code: def list getSearchTerms # NOTE: @params[:search_results] is an Array of product_data objects # returned by a search action. @results = @params[:search_results] if @results.nil? then # The default

Hi, I am facing issue with composite primary key In my gem file I have the below entries - gem 'rails', '>= 4.1.0.rc2' gem 'mysql2' gem 'rb-readline', "~> 0.5.1" gem 'sdoc', '~> 0.4.0', group: :doc gem 'spring', group: :development gem 'bcrypt', '~> 3.1.7' gem

Howdy, I''m a Rails beginner working on my first significant project with RoR. I''m trying to figure out how to validate a foreign key (you know, make sure the row actually exists.) However, validates_associated doesn''t seem to be what I want to use, nor does it work... -- BEGIN -- class City < ActiveRecord::Base has_many :schools belongs_to :state

Right now rails doesn''t support composite keys, that is id1, id2, and id3 are in the primary key of the table. Does anyone know if this is being discussed for future versions, or is it pretty much out of scope? -- Posted via http://www.ruby-forum.com/.

Hi All, How do I specify a composite primary key for a table in ActiveRecord? For example the table Recipe which has the primary key [cookie id, version number] where cookie id is also a foreign key referencing Cookie. Also: Thanks to Nic and Adam for helping with the Cookie -> Cooky problem. /Hugo --SQL * CREATE* *TABLE* `Raw_Materials`* (* id *INT*

Hey there, I''ve adjusted some of my many to many join tables recently to use a composite primary key based on the id''s in the two columns - instead of using a surrogate key. I just did a db:schema:dump, and it looks something like this: create_table "class_members", :id => false, :force => true do |t| t.integer "user_id", :default => 0,

I have two models User and Team. Also I have a register form where the new user fill in her data and choose a name for a Team. Well, in the user model there are several validations which work fine, but team model also have a validation for a uniqueness name that doesn''t fire up when she gives an existent team''s name. This is the flow it follows: /user/new -> it shows a

I have validates_uniqueness_of :name in my model which works fine when creating a record but doesn''t work when I edit the record. In other words it won''t let me create a record with the same name but I can go in after and update the field without a problem. Why would this happen? -Mike --~--~---------~--~----~------------~-------~--~----~ You received this message because you