Jonathan Rockway wrote:
* On Sat, Apr 05 2008, Alex Povolotsky wrote:
Jess Robinson wrote:
{ mycol => \'DEFAULT' }
perl with use strict should complaint on this. Without use strict -
complaint as well.
Uh... no.
Whooops... hmm... I'll see if DBI will get it and rewri
* On Sat, Apr 05 2008, Alex Povolotsky wrote:
> Jess Robinson wrote:
>> { mycol => \'DEFAULT' }
>
> perl with use strict should complaint on this. Without use strict -
> complaint as well.
Uh... no.
Regards,
Jonathan Rockway
--
print just => another => perl => hacker => if $,=$"
_
Jess Robinson wrote:
Well, how do you pass DEFAULT (not 'DEFAULT' string, but DEFAULT SQL
keyword) to DBI?
Using a literal string like that:
{ mycol => \'DEFAULT' }
perl with use strict should complaint on this. Without use strict -
complaint as well.
Alex.
On Sat, 5 Apr 2008, Alex Povolotsky wrote:
Jess Robinson wrote:
On Thu, 3 Apr 2008, Alex Povolotsky wrote:
Hello!
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with find_or_create
sub.
Are those columns also n
Jess Robinson wrote:
On Thu, 3 Apr 2008, Alex Povolotsky wrote:
Hello!
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with
find_or_create sub.
Are those columns also nullable, or not? If they're not, inserting
nul
Nigel Metheringham wrote:
On 3 Apr 2008, at 16:30, Alex Povolotsky wrote:
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with
find_or_create sub.
I've made and tested a simple patch, it looks working ok.
So the prob
Nigel Metheringham wrote:
On 3 Apr 2008, at 16:30, Alex Povolotsky wrote:
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with
find_or_create sub.
I've made and tested a simple patch, it looks working ok.
So the prob
Jess Robinson wrote:
On Thu, 3 Apr 2008, Alex Povolotsky wrote:
Hello!
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with
find_or_create sub.
Are those columns also nullable, or not? If they're not, inserting
nul
On Thu, 3 Apr 2008, Alex Povolotsky wrote:
Hello!
Attempt to insert into postgres table with undef's for columns with default
values yields an error. It is especially bad with find_or_create sub.
Are those columns also nullable, or not? If they're not, inserting
null/undef doesn't make se
On 3 Apr 2008, at 16:30, Alex Povolotsky wrote:
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with
find_or_create sub.
I've made and tested a simple patch, it looks working ok.
So the problem is that when you *exp
Hello!
Attempt to insert into postgres table with undef's for columns with
default values yields an error. It is especially bad with find_or_create
sub.
I've made and tested a simple patch, it looks working ok.
--- DBIx/Class/Storage/DBI/Pg.pm.orig 2007-08-12 01:07:58.0 +0400
+++ D
11 matches
Mail list logo
