search for: bigints

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,

Dear All, I have a centos 5 server running my mail and Dns working fine but when i try to do u yum ugrade or yum update it gives me lots of perl errors and it terminates OS is centos 5 (final) the part of errors reported --------------------------------- file /usr/lib/perl5/5.8.8/Math/BigFloat.pm from install of perl-5.8.8-18.el5_3.1 conflicts with file from package perl-Math-BigInt-1.86-1

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

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 am creating an app that will out grow an int(10) unsigned for the id field, ie. 4,294,967,295 records. What are my options, I have looked at the GUID plugin that lets you use a 32 char GUID, but I still want the id''s to be sequential, and (I think) that the overhead of searching a varchar field will be too big for such a large number of records. It does not appear you can use a

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

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

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

..., my unit tests were failing because when I copied the schema from the dev to the testing DB, it was copied as a plain int. This caused the large values in my unit tests to fail. I understand why the Migration framework doesn''t support this, since not all database engines might support BigInts, but it did catch me by surprise. So, my next idea was to convert the field to text. While I only need 13 characters in this field, using the change_column command with a :string type resulted in a varchar with a length of 255. I tried adding a :size => 13 option (and a :length => 13 opt...

Hi, Is there a way to tell to the migrations to use bigint(20) instead of int(11) for ids? Thanks, Fuad. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://wrath.rubyonrails.org/pipermail/rails/attachments/20060227/0896c124/attachment.html

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

Rsync people, I am preparing to overhaul my Web site's build system, and I am looking for a convenient way to collect files and directories from various places on my computer and put them at various locations inside a destination directory to be posted to my Web site. So far, my script has been running rsync once for each source, but this is too slow. Is there a way to get rsync to collect

currently dovecot dict is CREATE TABLE IF NOT EXISTS `quota` ( `username` varchar(100) COLLATE latin1_general_ci NOT NULL, `bytes` bigint(20) NOT NULL DEFAULT '0', `messages` int(11) NOT NULL DEFAULT '0', PRIMARY KEY (`username`) ) ENGINE=MyISAM DEFAULT CHARSET=latin1 COLLATE=latin1_general_ci; there is not field that says how much quota each user have, so one cant

I have come across an issue converting a JSON string in R (with either the package 'rjson' or 'RJSONIO') when big integers are included in the JSON string. A simple example of the problem is: > options(scipen=999) # To prevent representing the answer in scientific notation > json.str <- '{"bigInt":123456789123456789}' # Sample JSON string with big

Hi, according to the both discussions in the last few days I've tried to find a solution for Postfix with a PostgreSQL back-end. Its working nice for regular recipient addresses like user at example.com and addresses with an extension like user+foo at example.com. Alias addresses are currently ignored. * An alias may expand into multiple destinations. If one of this destinations is

https://bugzilla.samba.org/show_bug.cgi?id=9995 Summary: Rsync 3.1 dev : Product: rsync Version: 3.1.0 Platform: x64 OS/Version: Linux Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: dochitoai.vu at ladhyx.polytechnique.fr

someguy wrote: > Oh. One more thing: > > Paulo, while your working out how to do what Chris said (making usage > of bigints into library calls), wouldn't it just warm your heart to > document the process on the wiki? > > </wiki pimping> > > On Wed, Mar 25, 2009 at 9:16 AM, someguy > <just.s0m3.guy+llvmdev at gmail.com> wrote: > >> Oh. I see. That way the bigints don't ne...

On Mar 24, 2009, at 11:20 PM, someguy wrote: > I could be wrong, but I think that you may need to add a 'big-integer' > intrinsic type to llvm. No, please don't. GMP is just another library like libc, your front- end should just generate calls into it like any other library. This is similar to how we handle threading and many other "language features". -Chris