On 4/14/06 4:56 PM, Jesse Brown wrote:
> 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 hav
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
This is an important bug fix release for all RDBO users. There are no
new dependencies, but I also released a minor revision of Rose::DB.
Files sent to CPAN and on SF.net now:
http://sourceforge.net/project/showfiles.php?group_id=147570
Changes listed below.
-John
Rose::DB::Object:
0.71 (04.
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 wit
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 thin
On 14 Apr 2006 11:25:05 -0400, Ted Zlatanov <[EMAIL PROTECTED]> wrote:
> On 9 Mar 2006, [EMAIL PROTECTED] wrote:
>> package MyDBObject;
>>
>> use base 'Rose::DB::Object';
>> use Rose::DB::Object::Helpers qw(load_or_insert load_speculative);
>>
>> My question is, what methods should be in the helpe
On 14 Apr 2006 11:21:50 -0400, Ted Zlatanov <[EMAIL PROTECTED]> wrote:
> On 14 Mar 2006, [EMAIL PROTECTED] wrote:
>> Can you think of a good way to pass custom manager_args to individual calls
>> to a relationship accessor? Maybe a new read-only accessor type where
>> arguments can't possible be m
On 9 Mar 2006, [EMAIL PROTECTED] wrote:
> I'm adding a Rose::DB::Object::Helpers module to house all of the "extra"
> methods that people might want, but that I don't want crowding
> Rose::DB::Object itself. Example usage:
>
> package MyDBObject;
>
> use base 'Rose::DB::Object';
> use Rose::DB:
On 14 Mar 2006, [EMAIL PROTECTED] wrote:
> Can you think of a good way to pass custom manager_args to individual calls
> to a relationship accessor? Maybe a new read-only accessor type where
> arguments can't possible be meant to set values?
Maybe this will work:
$company->products({ id => 123
On 4/14/06 2:24 AM, Lucian Dragus wrote:
> I have a small patch to Rose::DB::Pg, in refine_dbi_column_info(), to
> recognize the float4 (real) columns as float types.
Thanks, applied.
-John
---
This SF.Net email is sponsored by xPML, a groun
10 matches
Mail list logo
