Cool! According to here:
http://dev.mysql.com/doc/refman/5.1/en/numeric-type-overview.html
A signed 'bigint' has the range of -9223372036854775808 to 9223372036854775807
(i.e. 2^63)
Unsigned 'bigint's have the range 0 to 18446744073709551615 (i.e. 2^64)
Which seems to match up exactly to 64 bit signed/unsigned ints in C.
Some of my code relies on 64 bit ints (very large file transfers, etc), and I
use the following to make sure...
# We require 64bit integers in order to work properly
# (large file offsets and sizes).
BEGIN {
use Config;
die "You do not have 64 bit integers available in your enviroment!"
unless $Config{'use64bitint'};
};
I would send a diff to RoseDBObject, but I haven't been fiddling with the
internals long enough to be effective I think.
Does this help?
On Fri, Apr 14, 2006 at 02:54:22PM -0400, John Siracusa wrote:
> On 4/14/06, Jesse Brown <[EMAIL PROTECTED]> wrote:
> > As a side note, I've noticed that mysql 'bigint' gets converted to a 20 byte
> > scalar, which is about as correct as it can get on 32bit machines. However,
> > on
> > perls with 64 bit integers, it should just be an int type. (more and more
> > common with x64 arch's)
> >
> > What is the prevailing opinion about things like this?
>
> Are MySQL's bigints really limited to 64 bits, or are they arbitrary
> precision? If they're really 64-bit, then what I'd need to make RDBO
> do the right thing is a way to determine if perl itself is compiled to
> use 64-bit integers internally. If I can detect that, then I can
> change the default column type mapping to map "bigint" to the Integer
> column class instead of the BigInt class.
>
> You can do this yourself right now, of course, using the
> column_type_class() method of the metadata class. If you're using the
> default metadata class, then that'd be:
>
> Rose::DB::Object::Metadata->column_type_class(
> bigint => 'Rose::DB::Object::Metadata::Column::Integer');
>
> Put that call anywhere where it'll get run before you initialize your
> first RDBO class to make all the bigint columns use the Integer column
> class.
>
> -John
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
> _______________________________________________
> Rose-db-object mailing list
> Rose-db-object@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rose-db-object
-----------------------------------------------------------
This message may contain confidential and/or privileged
information. This information is intended to be read only
by the individual or entity to whom it is addressed. If
you are not the intended recipient, you are on notice that
any review, disclosure, copying, distribution or use of
the contents of this message is strictly prohibited. If
you have received this message in error, please notify the
sender immediately and delete or destroy any copy of this
message.
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Rose-db-object mailing list
Rose-db-object@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rose-db-object
