On 6/2/07, John Siracusa <[EMAIL PROTECTED]> wrote:
Just to chime in, we have a similar problem at work: selecting a row with an
LVARCHAR column in it causes a segfault(!) for us. This happens on two of
our machines, but does not happen on a third. We have yet to narrow down
the
On 6/2/07 5:42 PM, John Siracusa wrote:
> Just to chime in, we have a similar problem at work: selecting a row with an
> LVARCHAR column in it causes a segfault(!) for us. This happens on two of
> our machines, but does not happen on a third. We have yet to narrow down
> the exact
Just to chime in, we have a similar problem at work: selecting a row with an
LVARCHAR column in it causes a segfault(!) for us. This happens on two of
our machines, but does not happen on a third. We have yet to narrow down
the exact differences. I'll post more when I have more information. In
On 3/25/06 6:24 PM, John Siracusa wrote:
> I expect the following two pieces of code to give the same result. One is
> SQL, fed directly to Postgres using the psql command-line tool, and the
> other is Perl code using DBI. Before I file this as a bug in DBD::Pg, I
> want to make sur
On 3/26/06 4:00 AM, Martin J. Evans wrote:
> Tom Mornini wrote:
>> You need to turn AutoCommit off with:
>>
>>> my $dbh = DBI->connect('dbi:Pg:dbname=test', 'postgres', '...',
>>>{ PrintError => 1, RaiseError => 0,
>>> AutoCommit => 0 });
>
> You should not have to
I expect the following two pieces of code to give the same result. One is
SQL, fed directly to Postgres using the psql command-line tool, and the
other is Perl code using DBI. Before I file this as a bug in DBD::Pg, I
want to make sure it's not a "feature" of DBI or something.
In the code, note
/wiki/
* Documentation on CPAN:
http://search.cpan.org/dist/Rose-DB-Object/
-John
---
0.601 (01.01.2006) - John Siracusa <[EMAIL PROTECTED]>
* Fixed some incorrect deep join tests.
* Reduced the number of Postgres database connections used in the test
suite in order to avoid hitting
On 12/1/05 10:00 PM, Mark wrote:
> For example, I have a ~10 billion row, ~1TB table, time partitioned,
> with about 10-20 million rows per day. I need "interactive"
> performance (2-10 seconds) response on queries that are confined
> to 2-3 days data. Obviously, I can't scan a TB table each time
On 12/1/05 7:17 PM, Todd Hepler wrote:
> Basically I'm looking for something like this snippet:
>
> @[EMAIL PROTECTED] = ();
> $sth->bind_columns(map { \$results{$_} } @fields);
>
> wrapped in a nice little interface.
Just an unrelated tip: the above can be done a bit more idiomaticall
0.51 (11.20.2005) - John Siracusa <[EMAIL PROTECTED]>
* Added auto-initialization of relationships.
* Added loader.
Rose::DB::Object now has a "loader." (I don't really like that name, but
Class::DBI::Loader seems to have set terminology expectations, so there yo
nsive
tutorial:
perldoc Rose::DB::Object::Tutorial
It's not a replacement for the reference-style documentation, but it does
give a nice overview of the major features, and how best to use them.
-John
---
0.50 (11.17.2005) - John Siracusa <[EMAIL PROTECTED]>
* Added optional
On 11/13/05 4:04 PM, Tyler MacDonald wrote:
> Is there a clean way to detect whether InnoDB support is available
> on the MySQL server? The best I've been able to come up with so far, is
> attempting to create a temporary table with the "TYPE=InnoDB" argument and
> testing to see if it fail
That w
On 9/26/05 5:01 AM, Tim Bunce wrote:
> Anyone else have a DBI subclassing story to tell?
My story is short: I never seriously attempted it because I knew how scary
and non-standard DBI was internally. Several times in my misspent youth I
wanted to do something "simple" like:
package MyDBI;
0.075 (09.19.2005) - John Siracusa <[EMAIL PROTECTED]>
* Added support for "many to many" relationships to Manager's
"with_objects" and "require_objects" parameters.
* Corrected a bug that could cause missing sub-objects when
Some big changes this time:
0.074 (09.15.2005) - John Siracusa <[EMAIL PROTECTED]>
* Repurposed the "with_objects" Manager parameter to do explicit
LEFT OUTER JOINs instead of implicit inner joins.
* Added "require_objects" Manager parameter to fill
I've just started a mailing list for my RDBMS-OO module, Rose::DB::Object.
The list is for users as well as developers interested in extending or
contributing to the code.
Rose::DB::Object is the latest of many RDBMS-OO modules that I've created,
but it's the first that I've decided to put up on C
On 8/21/05 10:38 PM, [EMAIL PROTECTED] wrote:
> I'm using DBD:DB2.
> Maybe quatation (') rwapping data must be dropped, and
> "CURRENT TIMESTAMP" keyword will be treated.
>
> my @new_values = ();
> my @place_holders =
> map {
> if (/^CURRENT TIMESTAMP$/) {
> $_;
> } else {
>
On 8/17/05 5:39 AM, Tim Bunce wrote:
> On Tue, Aug 16, 2005 at 03:58:54PM -0400, John Siracusa wrote:
>> I think it'll take years, and much actual production experience building
>> Perl 6 modules before the community learns what works and what doesn't for a
>> Perl
On 8/16/05, Tim Bunce <[EMAIL PROTECTED]> wrote:
> I was a little dissapointed that there wasn't greater focus on using
> Perl6 features - especially as it would have helped kick-start my own
> understanding of Perl6 topics that I expect to be significant (such as
> Roles and Pairs, to pick two at
> At 8:24 PM + 7/21/05, Terrence Brannon wrote (on poop-group):
>>> At 7:05 AM -0400 7/19/05, John Siracusa wrote:
>>>> I use a module (Rose::DB) that parses and formats db-specific column values
>>>> for me: various kinds of dates, "SET"s, arr
On 12/7/04 5:40 PM, Tim Bunce wrote:
> On Tue, Dec 07, 2004 at 04:40:51PM -0500, John Siracusa wrote:
>> That's what DBI wrappers do, and I have one of those too. But my DBI
>> wrapper reads its connection information for each "logical" data source from
>&g
On Wed, 08 Dec 2004 10:21:35 +1300, Sam Vilain <[EMAIL PROTECTED]> wrote:
> I think that this information should be removed from most programs
> altogether. They should just have to specify a logical data source
> (possibly including a schema version), then a module with a config file
> maps that
On Tue, 7 Dec 2004 10:58:56 +0100, Henrik Tougaard <[EMAIL PROTECTED]> wrote:
> Ingres, like Informix and (I think) Oracle, does'nt have the concept
> of 'host' or 'port', using other ways of adressing remote databases.
So? AFAICT, what we've been talking about is simply a list of name/value
pair
On Wed, 1 Dec 2004 18:39:00 +, Tim Bunce <[EMAIL PROTECTED]> wrote:
> FWIW, the reason I'm digging here is because I agree there may be
> some value in the DBI supporting something along these lines, but
> I need a better understanding of the underlying issues. More real-
> world examples would
24 matches
Mail list logo
