similar to: rake db:schema:dump doesn't produce composite primary key instructions

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

Hi, As I understand, composite primary keys aren''t supported in ActiveRecord yet. May I ask if there are plans for this feature? Better yet, if this feature is under development, how''s the progress going? I''m not trying to use legacy databases. I tend to think that using multiple integer column id''s (composite primary key) are often natural way to

I ran into a "chicken before the egg" problem where a gem was expecting the tables to be present when loaded which was fine until you try and build the db from scratch using db:setup. When it hits db:schema:load the environment loads and the gem errors out as the tables aren''t present. I made a custom task that connected to ActiveRecord and then loads the schema file. Using

I have tables with double as their field''s datatype. When I ran db:schema:dump, Rails changed all of these double to float. I would like to know why, and if there is anyway I could preserve the datatype. Thanks a lot, Chris --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk"

Hello! I''ve submitted a patch to work around a problem when multiple schemas are included in the search_path in database.yml for PostgreSQL databases. (Long story short: the pg_dump --schema flag only accepts a single schema.) http://dev.rubyonrails.org/ticket/6665 While I''ve tested the regex pattern used to check for multiple schemas, I''m unsure of how to

I am thinking that I have found a bug in Rails migrations. My app is using UUIDtools to generate guids for primary keys. To do this I pass :id=>false and then create my own id column as shown below. Next I leverage "execute" to create an index. It seems to work fine. The table in MySql is perfect. However the ID column and primary key on the ID column are not in the schema.rb file I

Subject says it all: rake doesn''t know about db:fixtures:dump. When I try, I get this: Don''t know how to build task ''db:fixtures:dump'' I thought this was a standard feature that ships with rake- any idea why it''s missing, and how I can reinstall it? Here''s the environment: Ruby version 1.8.4 (powerpc-darwin8.6.0) RubyGems

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

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

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:

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*

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/.

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

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

Hey, I am new to this and I thought I had finally set up everything perfectly after three days of trying to configure it. However I run this command: rake db:schema:load and I get an error "syntax error on line 23, col 11: `''". The error however is now with the schema it''s with the ruby install itself as you can see with the trace I ran:

My model consists of users and tasks (m:n), the relation is stored in a seperate table sharedtabs (that contains some extra fields). Between tabs and tasks there is a 1:n relation. I have trouble writing my seed.rb: works: (1) tab = Tab.create(:name => ''Admin'', :category => 0) tab.tasks.create(:name => ''Admin_Tab1_Private Task 1'') works: (2)

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''

Hello. I''m working the "proper way" with creating the initial db schema via migrations and db/schema.rb. However, I have a bit of a special need, and need to know if anyone knows the solution to this; I need a sequence that is common to several tables - a "data id" that gives a sort of unique object number to every row in every table. Some associated tables (a

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:

Whenever I run rake db:migrate I get the following "error": antrover:~/Sway/Projects/mi7/branches/sway_dev_mi7 dhoefler$ rake db:migrate (in /Users/dhoefler/Sway/Projects/mi7/branches/sway_dev_mi7) /usr/local/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/validations.rb:334: warning: `*'' interpreted as argument prefix