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.
Am 05.04.2008 um 18:00 schrieb Sebastian Willert:
Unfortunately it's not as easy as this. Off the top of my head:
transactional isolation just prevents dirty reads wrt. this problem,
i.E. reading an inconsistent state.
Understood. But the transaction could include a read which checks
whether
On Sat, 2008-04-05 at 17:06 +0200, Moritz Onken wrote:
> Am 04.04.2008 um 16:56 schrieb Sebastian Willert:
> >
> > Guilty as charged, your honor. I still have an half-backed
> > implementation of DBIx::Class::Tree::NestedSet laying around, that
> > I've
> > almost forgotten about. In my defense,
Am 04.04.2008 um 16:56 schrieb Sebastian Willert:
Guilty as charged, your honor. I still have an half-backed
implementation of DBIx::Class::Tree::NestedSet laying around, that
I've
almost forgotten about. In my defense, I'd stopped working on it
because
I believe we'd need a good RDBMS-ind
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
