fREW Schmidt wrote:
Hi all!
We are dealing with some weird issues because our database has silly
column names. Specifically speaking we have a column called 'user'.
user is a reserved word in T-SQL (we are using SQL Server.) Anyway,
this is the error we get:
DBIx::Class::ResultSet::f
Brandon Black wrote:
> On 10/22/07, Jesper Krogh <[EMAIL PROTECTED]> wrote:
>>> On 10/20/07, Jesper Krogh <[EMAIL PROTECTED]> wrote:
>>> I'll work out a patch for this sometime this weekend, we'll see on IRC
>>> where it should go, as far
> On 10/20/07, Jesper Krogh <[EMAIL PROTECTED]> wrote:
> I'll work out a patch for this sometime this weekend, we'll see on IRC
> where it should go, as far as who it breaks, etc.
Let me know when there is something to test?
Darren Duncan wrote:
> At 10:43 AM +0200 10/20/07, Jesper Krogh wrote:
>> It was my impression that passing AutoCommit => 1 goes directly to the
>> $dbh (correct me if I'm wrong?)
>>
>> And that AutoCommit => 1 makes every UPDATE/INSERT/DELETE in the
&
at, when", then you can either pass on the webuser
explicitly to every database query or use the authenticatied user in the
database. Which gives a nice possiblity to make a "log table" with
"old-data",who,lifetime just updated
Darren Duncan wrote:
> At 8:18 PM +0200 10/20/07, Jesper Krogh wrote:
>> AutoCommit => 1 and txn_do does not give me the option to intentionally
>> do a ROLLBACK, does it?
>
> Yes it does. Just throw an exception (die) in your code block passed to
> txn_do wh
nection pre-request from Catalyst,
that may be the reason why I never stumbled upon that problem.
In this application the "web-authenticated-user" is also the
"database-user", so a "connection per request" is required.
(Or at least I havent seen how to change the user ove
Brandon Black wrote:
> On 10/20/07, Jesper Krogh <[EMAIL PROTECTED]> wrote:
>> Brandon Black wrote:
>>> What AutoCommit => 1 does is make it so that if you aren't in an
>>> explicit transaction at the DBI (or DBIC) level, every statement is
>>> c
ons before doing any work
> (txn_begin or txn_do), and basically dropping support for AutoCommit
> => 0 and implicit txn starts.
That sounds reasonable to me.
Jesper
--
Jesper Krogh, [EMAIL PROTECTED]
___
List: http://lists.scsys.co.uk/cg
Matt S Trout wrote:
> On Fri, Oct 19, 2007 at 10:28:38AM +0200, Jesper Krogh wrote:
>> AutoCommit is 0 .. you can see it above, thats by intention.
>
> AutoCommit 0 has been considered undefined for DBIC for some time.
I've failed to notice that.
> DBIC provides safe tran
> On 10/18/07, Jesper Krogh <[EMAIL PROTECTED]> wrote:
>> There is a change in the behaviour of
>> $schema->txn_rollback from 0.07* to 0.08*
>>
>>
>> $ DBIC_TRACE=1 perl -I/tmp/0.07003/lib/ ./test.pl
>> DBIx::Class version: 0.07003
>> SELECT &
e get a warning, probably because the $schema->txn_rollback in
the script doesn't get to the database.
The script looks like this.
$ cat test.pl
#!/usr/bin/perl
#
use strict;
use warnings;
use lib "lib/";
use Testdb;
print "DBIx::Class version: " . $DBIx::Class::VERSIO
12 matches
Mail list logo
