similar to: BIGINT IDs in migrations

hi, just wondering do migration support MySQL BIGINT ? what if i wanna create a migration with BIGINT ? should i use SQL directly ? kiwi -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to

I have to create Migration file form Mysql DB But I want type of Migration equivalent with Mysql DB (example : in Mysql with type Bigint and in Migration will have type Int(20) or Bigint) Could You help me solve this Problem? Thanks -- Posted via http://www.ruby-forum.com/. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To

Dear Gurus on Rails! How do I change the behaviour of one method in ActiveRecord::ConnectionAdapters::SchemaStatements ? Full story: I''d like to mangle ActiveRecord::ConnectionAdapters::SchemaStatements so when it creates a new sql table, it also (optionally) creates my created_at, deleted, key_id, session_id etc columns that I use on basically all tables. It would not be DRY to repeat

Hi - I have a simple R script that inserts values into a Postgres table to generate a record that autogenerates a bigint unique ID (basically, a customized bigserial value). When I query the table to retrieve the bigint value, the value returned is not the same as the value created in the database (as evidenced by a direct query of the database table via pgAdmin). e.g. the value created should

Howdy Y''all, I was thrilled to recently discover migrations, as that framework addresses a common problem in an elegant way. I have, however, gotten tripped up a bit as I''ve worked with them. The first problem I encountered was that, though I was using a BigInt data type in a field in my dev database, my unit tests were failing because when I copied the schema from the dev

Hello, After a (bad) first try some months ago, I'm trying again to use RODBC package instead of DBI+RMySQL packages to populate MySQL database. The main command is sqlSave(channel, data_df, tablename, append=T, rownames=FALSE, colnames=FALSE, fast=FALSE, varTypes=vartypes) where data_df is the data.frame I want to save and vartypes is obtained following the tip given here

I had to move a perl script from an old server to a new one. Both the old and new servers are running "CentOS release 5.10 (Final)" and perl v5.8.8. (But the problem I'm running into appears to be a package management problem and not a Perl problem which is why I'm posting it to a CentOS list.) The line of code in the script that attempts to open a Net::SFTP connection,

The MySQL/Ruby library doesn''t properly handle inserts into tables with the primary key being a BIGINT If the ID returned to the MySQL/Ruby library is LARGER than the INT range, the value is returned to Ruby truncated and incorrect. This is then passed up to ActiveRecord and into the id field of your model. The actual INSERT worked properly and when do you an ActiveRecord find for the

There''s some confusion as to what the :limit option should mean when used against integer columns in migrations. Patch #2900 added support for limits in PostgreSQL mapping mapping limit < 4 to smallint, > 4 to bigint, and anything else to integer (so the limit is the number of bytes) However, the mysql adapter uses limit to specify the ''display width'' in digits,

Dear Group, if anyone has experience with the RMySQL Package maybe this behaviour is know: Reading data from a table into R the fields with datatype bigint(20) unsigned are transformed in some way: e.g. the query "select * from orders where userid = 14929859848712890325" selects the correct case but in R the userid is changed to 14929859848712890368. What happened here? This

Hello, I''m just taking a look at migrations, seems like a fantastic way to maintain the database. I am wonder if there is a way to maintain what I''ll call "reference data" along with the migrations. A lot of times in apps your have tables that have pretty static data, often used to generate select lists. Is there a way to insert the reference data into these tables

Is there any work being done to add support for defining foreign keys in ActiveRecord Migrations? If not is it something that people would find useful or do most people here believe in the "Application Database" style over the "Integration Database" style [1] as defined by Fowler? I''d love to see support for foreign keys in Migrations. For selfish reasons

Hi. I''m using a migration to extract data from one table, to another. In the process I also convert ip-adresses to integers, for insertion in the new table. Problem is that migrations doesn''t seem to handle large numbers very well. The conversion works fine from the script/console, but when running it from migrations only very low IP-ranges "make it thru".

Hi I''d like to have a varchar primary key named id instead of the default int id. Does anyone knows how to specify this from migrations ? Should I also specify something in the model class ? thanks! Thibaut -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060312/797bca4b/attachment.html

I followed the Wiki instructions for setting up *yum-priorities*. I added the rpmforge repo I installed clamd without a problem. Now when I go to update I get conflicts with perl-Math-BigInt. Is the only solution to uninstall the base version and then install the rpmforge version? According the the wiki "Packages from repositories with a lower priority will never be used to upgrade

I am trying to start my first project after going though the Depot application in prog prog''s book. For some reason one of my migrations keeps bombing. I just try to setup a couple tables with some default information and even with changing the name of the second table and other minor tweaks it just does not work. I am connected to the db, the first table does get filled out. Any help

Hi All Please excuse me if my questions sound silly. I have developed a rails app with an existing legacy schema and now with changes in customer requirements, I need to change the schema. The legacy (schema) database has > 250K. What I would like to know is 1. Is it possible to migrate the data along with migrating the schema if use Migrations? If it is possible can somebody point me to an

I read in various places that although migrations aren''t transactional, all you need to do is wrap you migration method in "ActiveRecord:: Base.connection.transaction do" to make the self.up or self.down transactional. In my experience (Rails + PostgreSQL), this doesn''t work very well. If my migration hits an exception, any tables that were touched remain modified.

I''ve got a MySQL app, which I''m moving to a new server which is using Postgres. This seems like the perfect application of migrations. (Note: I don''t mean "using migrations to switch from MySQL to Postgres" so much as "Hey, I''ve _been_ using migrations all along, and this is where I cash in".) There were some odd bugs when working with the

The new chapter in Agile Web Development with Rails talks about using migrations to load data from fixtures. This is a great idea, I''ve wanted to do this. This allows you a good way to create sample data that you can use during development, testing or demoing of an application. My question is how do you keep it separated from the real data? For example, say you have a User and Account