Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2009-06-16 Thread Tomas Doran
Sergio Salvi wrote: I've applied both patches into this branch: http://dev.catalyst.perl.org/svnweb/Catalyst/browse/branches/Catalyst-Plugin-Session/both/ Hi, sorry for the very late followup on this, but it's been noted that the documentation wasn't adjusted to reflect the changes made. I d

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-12-12 Thread Sergio Salvi
On Thu, Dec 11, 2008 at 12:04 PM, Sergio Salvi wrote: > On Thu, Nov 20, 2008 at 4:49 PM, Tobias Kremer wrote: >> On 20.11.2008, at 21:16, Sergio Salvi wrote: >>> >>> I still think the final solution (besides finding a way to make >>> find_or_create() atomic), is to store flash data the session ro

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-12-11 Thread Sergio Salvi
On Thu, Nov 20, 2008 at 4:49 PM, Tobias Kremer wrote: > On 20.11.2008, at 21:16, Sergio Salvi wrote: >> >> I still think the final solution (besides finding a way to make >> find_or_create() atomic), is to store flash data the session row >> (either on the same column of session or on a new, dedic

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-11-20 Thread Tobias Kremer
On 20.11.2008, at 21:16, Sergio Salvi wrote: I still think the final solution (besides finding a way to make find_or_create() atomic), is to store flash data the session row (either on the same column of session or on a new, dedicated column). Sergio++ FWIW, I rolled my own flash mechanism whi

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-11-20 Thread Sergio Salvi
On Fri, Sep 26, 2008 at 3:49 PM, Daniel Westermann-Clark <[EMAIL PROTECTED]> wrote: > On 2008-08-26 09:47:59 +0200, Tobias Kremer wrote: >> a) Patch Catalyst::Plugin::Session::Store::DBIC to wrap the flash >>functionality in a transaction (of course, this must be >>configurable). > > I've

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-09-26 Thread Daniel Westermann-Clark
On 2008-08-26 09:47:59 +0200, Tobias Kremer wrote: > a) Patch Catalyst::Plugin::Session::Store::DBIC to wrap the flash >functionality in a transaction (of course, this must be >configurable). I've released a new version which includes this functionality: 0.07 Wed Sep 24 17:08:34 EDT 2008

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-09-05 Thread Tobias Kremer
Quoting Jonathan Rockway <[EMAIL PROTECTED]>: > * On Wed, Aug 27 2008, Tobias Kremer wrote: > > We definitely should! IMHO five queries per request to the database just > > for the session and flash stuff is inacceptable. > If your app is really slowed by the number of queries to load > session/fla

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-09-04 Thread Jonathan Rockway
* On Wed, Aug 27 2008, Tobias Kremer wrote: > Quoting Daniel Westermann-Clark <[EMAIL PROTECTED]>: > >> On 2008-08-26 14:18:18 +0200, Tobias Kremer wrote: >> > Just out of pure curiosity: Why is it that there are dedicated >> > "flash:" entries in the storage for the flash? Wouldn't the >> > sessio

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Matt S Trout
On Wed, Aug 27, 2008 at 10:41:11AM +0200, Tobias Kremer wrote: > Quoting Moritz Onken <[EMAIL PROTECTED]>: > > Am 27.08.2008 um 10:19 schrieb Tobias Kremer: > > > Ok, a second glance (after the first coffee) revealed that the > > > separation is indeed there :) The question is, why? > > > > Just gu

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Tobias Kremer
Quoting Moritz Onken <[EMAIL PROTECTED]>: > Am 27.08.2008 um 10:19 schrieb Tobias Kremer: > > Ok, a second glance (after the first coffee) revealed that the > > separation is indeed there :) The question is, why? > > Just guessing: > not every request has its own session object. There are users wit

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Moritz Onken
Am 27.08.2008 um 10:19 schrieb Tobias Kremer: Quoting Tobias Kremer <[EMAIL PROTECTED]>: Quoting Daniel Westermann-Clark <[EMAIL PROTECTED]>: The "flash:" rows were used for compatibility with Store::DBI. We can break compatibility if people find the it not very useful. I have to admit t

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Tobias Kremer
Quoting Tobias Kremer <[EMAIL PROTECTED]>: > Quoting Daniel Westermann-Clark <[EMAIL PROTECTED]>: > > The "flash:" rows were used for compatibility with Store::DBI. We can > > break compatibility if people find the it not very useful. > I have to admit that I don't understand what compatibility w

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Tobias Kremer
Quoting Daniel Westermann-Clark <[EMAIL PROTECTED]>: > On 2008-08-26 09:47:59 +0200, Tobias Kremer wrote: > > Please note, that this is ONLY happening with the flash part - my > > sessions work 100% accurate all the time! > How are you interacting with the flash vs. your sessions? Could you > prov

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-27 Thread Tobias Kremer
Quoting Daniel Westermann-Clark <[EMAIL PROTECTED]>: > On 2008-08-26 14:18:18 +0200, Tobias Kremer wrote: > > Just out of pure curiosity: Why is it that there are dedicated > > "flash:" entries in the storage for the flash? Wouldn't the > > session be enough? > > The "flash:" rows were used for co

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-26 Thread Daniel Westermann-Clark
On 2008-08-26 09:47:59 +0200, Tobias Kremer wrote: > a) Patch Catalyst::Plugin::Session::Store::DBIC to wrap the flash >functionality in a transaction (of course, this must be configurable). >Advantages: > - Easy to implement > - Most sensible solution. >Disadvantages: >

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-26 Thread Daniel Westermann-Clark
On 2008-08-26 14:18:18 +0200, Tobias Kremer wrote: > Just out of pure curiosity: Why is it that there are dedicated > "flash:" entries in the storage for the flash? Wouldn't the > session be enough? The "flash:" rows were used for compatibility with Store::DBI. We can break compatibility if peopl

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-26 Thread Tobias Kremer
Quoting Tobias Kremer <[EMAIL PROTECTED]>: > just wanted to inform you that switching from MyISAM to InnoDB for the > session table does NOT solve the "duplicate entry" problem when > using flash() :( Just out of pure curiosity: Why is it that there are dedicated "flash:" entries in the storage f

Re: [Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-26 Thread Peter Corlett
On Tue, Aug 26, 2008 at 09:47:59AM +0200, Tobias Kremer wrote: [...] > b) Patch DBIx::Class's find_or_create() method and reverse its order >(insert first, check for duplicate, then select). >Disadvantages: > - Not that easy to implement because every database returns >a differ

[Catalyst] Duplicate entries with C::P::Session::Store::DBIC and MySQL - new findings

2008-08-26 Thread Tobias Kremer
Hey guys, just wanted to inform you that switching from MyISAM to InnoDB for the session table does NOT solve the "duplicate entry" problem when using flash() :( I really can't believe that me and 3 or 4 others are the only people experiencing this problem! We're getting close to 400 of those err