On Thu, Jan 31, 2008 at 04:01:27PM +0530, Rajesh Pethe wrote:
Matt S Trout wrote:
On Wed, Jan 30, 2008 at 09:31:27PM +0530, Rajesh Pethe wrote:
I have also faced this problem with newer version of DBIx (0.08008).
Old version works fine.
Then provide us with enough information to
On Thu, Jan 31, 2008 at 11:09:19AM +0100, Zbigniew Lukasiak wrote:
On Jan 31, 2008 10:39 AM, Matt S Trout [EMAIL PROTECTED] wrote:
On Wed, Jan 30, 2008 at 07:57:02PM +0100, Zbigniew Lukasiak wrote:
Hi Matt,
You are a mystery to me - but I'll try to comply and interleave my
comments
On Feb 1, 2008 9:31 AM, Matt S Trout [EMAIL PROTECTED] wrote:
On Thu, Jan 31, 2008 at 11:09:19AM +0100, Zbigniew Lukasiak wrote:
On Jan 31, 2008 10:39 AM, Matt S Trout [EMAIL PROTECTED] wrote:
On Wed, Jan 30, 2008 at 07:57:02PM +0100, Zbigniew Lukasiak wrote:
Hi Matt,
You are a
On Fri, Feb 01, 2008 at 01:28:07PM +0100, Cedric Boudin wrote:
Dear members of the list.
I have a custom resultsource calling a db function with 4 input
parameters returning a set of rowtypes.
This resultsource is build as described in
DBIx::Class::Manual::Cookbook
Arbitrary SQL through
Dear members of the list.
I have a custom resultsource calling a db function with 4 input
parameters returning a set of rowtypes.
This resultsource is build as described in
DBIx::Class::Manual::Cookbook
Arbitrary SQL through a custom ResultSource
case a)
When I use this resultsource to get a
I asked a long time back about engine specific escape sequences to
sanitize LIKE queries. I got pointed to a neat snippet from the DBI
docs but mostly heard don't use search (or search_like).
$esc = $dbh-get_info( 14 ); # SQL_SEARCH_PATTERN_ESCAPE
$search_pattern =~
Hi Matt,
Will I hear a 'thank you' from you? I mean I've spotted the bug, sent
test cases, analyzed the code and tried to explain how it happened
(perhaps that was not a good explanation - but a gifted programmer as
you should be capable of analyzing the code directly without my help),
and your
On Sat, Feb 02, 2008 at 07:14:09AM +0100, Zbigniew Lukasiak wrote:
Hi Matt,
Will I hear a 'thank you' from you? I mean I've spotted the bug, sent
test cases, analyzed the code and tried to explain how it happened
(perhaps that was not a good explanation - but a gifted programmer as
you
