On Thu, Nov 15, 2012 at 10:38 AM, Peter Rabbitson wrote:
> On Thu, Nov 15, 2012 at 10:31:21AM -0300, Fernan Aguero wrote:
> > So, apparently the problem is calling delete() right on the resultset
> > object. For some reason that eludes me, DBIC is not fully qualifying the
> > table in this case.
>
On Wed, Nov 14, 2012 at 5:56 PM, Francisco Obispo wrote:
> Use:
>
> $c->model('GUS::WebappSession') as the name.
So, it was a good suggestion after all ... it didn't work at first, and I
think this led me to (maybe) a possible fix
This doesn't work:
sub remove_sessions : Private {
my ( $sel
On Wed, Nov 14, 2012 at 5:56 PM, Francisco Obispo wrote:
> Use:
>
> $c->model('GUS::WebappSession') as the name.
>
And where would I put this?
I'm not dealing myself with the session data. I'm relying and delegating
all this to Session, Session::Store::DBIC, and Session::State::Cookie
That's w
Use:
$c->model('GUS::WebappSession') as the name.
or in the config:
dbic_class GUS::WebappSession
id_field id
storage_field session_data
expires_field expires
need_commit 0
expires 3600
verify_address 1
francisco
On Nov 14, 2012, at 12:51 PM, Fernan Aguero wrote:
>
> The
On Wed, Nov 14, 2012 at 3:09 PM, Francisco Obispo wrote:
> Did you use the dbicdump script (or myapp_create.pl model) command to
> create the schema files?
>
> I would suggest you look to see how the 'sessions' table was created and
> use that as the name for the relation.
>
> regards
>
I did no
Did you use the dbicdump script (or myapp_create.pl model) command to create
the schema files?
I would suggest you look to see how the 'sessions' table was created and use
that as the name for the relation.
regards
On Nov 14, 2012, at 7:07 AM, Fernan Aguero wrote:
> Of course, I can reprod
On Wed, Nov 14, 2012 at 10:07 AM, Fernan Aguero wrote:
[...]
> Thanks Alejandro for the quick response. I still think that this is
> exposing a bug in Session::Store::DBIC or Session::Store::Delegate. They
> should use whatever qualified name is given in the DBIC class ... but I'm
> not sure whe
On Wed, Nov 14, 2012 at 11:36 AM, Alejandro Imass wrote:
> On Wed, Nov 14, 2012 at 7:45 AM, Fernan Aguero wrote:
>
>> Hi,
>>
>> I'm having this issue with my catalyst app where the session table is
>> not fully qualified in the generated SQL statement:
>>
>
> [...]
>
>
>> The sessions table lives
On Wed, Nov 14, 2012 at 7:45 AM, Fernan Aguero wrote:
> Hi,
>
> I'm having this issue with my catalyst app where the session table is
> not fully qualified in the generated SQL statement:
>
[...]
> The sessions table lives in my PostgreSQL database in a separate
> schema 'webapp'.
>
> So I woul
