<br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 14, 2012 at 5:56 PM, Francisco Obispo <span dir="ltr"><<a href="mailto:fobispo@isc.org" target="_blank">fobispo@isc.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Use:<br>
<br>
$c->model('GUS::WebappSession') as the name.<br></blockquote><div><br></div><div>And where would I put this? </div><div><br></div><div>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</div>
<div><br></div><div>That's why I'm saying that somewhere within these modules, they are failing at getting 'GUS::WebappSession'. They seem to be using a hardwired 'sessions' table ...</div><div><br>
</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
or in the config:<br>
<br>
<br>
<Plugin::Session><br>
dbic_class GUS::WebappSession<br>
id_field id<br>
storage_field session_data<br>
expires_field expires<br>
need_commit 0<br>
expires 3600<br>
verify_address 1<br>
</Plugin::Session></blockquote><div><br></div><div>My config is simpler, but still identical to what you propose:</div><div><br></div><div><div>[fernan@optima] cat tcsnp_local.yml </div><div>Model::GUS:</div><div> schema_class: GUS</div>
<div> connect_info:</div><div> - dbi:Pg:dbname=tcsnp</div><div> - fernan</div><div> - //PASS//</div><div> - AutoCommit: 1</div><div><br></div><div>session:</div><div> dbic_class: GUS::WebappSession</div><div>
cookie_name: tcsnp_cookie</div><div> cookie_expires: 0</div></div><div> </div><div>This is clearly not the issue. All other SQL statements are being generated correctly, e.g. using DBIC_TRACE=1</div><div><div><br></div>
<div><font face="courier new, monospace">[info] tcsnp powered by Catalyst 5.90018</font></div><div><font face="courier new, monospace">HTTP::Server::PSGI: Accepting connections at <a href="http://0:3006/">http://0:3006/</a></font></div>
</div><div><div><font face="courier new, monospace">BEGIN WORK</font></div><div><font face="courier new, monospace">SELECT <a href="http://me.id">me.id</a>, me.session_data, me.expires FROM webapp.sessions me WHERE ( <a href="http://me.id">me.id</a> = ? ): 'session:eff3bb1616f1ee3341477c4d1056c51c7ed826a6'</font></div>
<div><font face="courier new, monospace">COMMIT</font></div><div><font face="courier new, monospace">[info] *** Request 1 (0.167/s) [14993] [Wed Nov 14 18:22:13 2012] ***</font></div></div><div><div><font face="courier new, monospace">[debug] Path is "genes"</font></div>
<div><font face="courier new, monospace">[debug] "GET" request for "genes" from "127.0.0.1"</font></div><div><font face="courier new, monospace">[debug] Rendering template "genes/<a href="http://search.tt">search.tt</a>"</font></div>
<div><font face="courier new, monospace">[debug] Applying HTML page layout wrappers to genes/<a href="http://search.tt">search.tt</a></font></div><div><font face="courier new, monospace">[debug] Found sessionid "eff3bb1616f1ee3341477c4d1056c51c7ed826a6" in cookie</font></div>
<div><font face="courier new, monospace">[debug] Response Code: 200; Content-Type: text/html; charset=utf-8; Content-Length: 25221</font></div><div><font face="courier new, monospace">[info] Request took 0.331861s (3.013/s)</font></div>
</div><div><br></div><div>Here you can see that the table is fully qualified with the schema name as expected.</div><div><br></div><div>It is only at the DELETE statements that this is failing.</div><div><br></div><div>--</div>
<div>fernan</div></div>
</div>