On Tue, Jul 29, 2008 at 5:21 AM, Daniel McBrearty <[EMAIL PROTECTED]
> wrote:
> my 0.05 (possibly a bit OT) :
Off-topic or not, I think these are interesting and valid questions.
> I looked previously at a few ways of adding forums etc to the site
> using 3rd party code, indeed there are many
On 2008-07-28 22:33:44 +0100, Matt S Trout wrote:
> > Is there anything speaking against wrapping line 52 of the DBIC
> > backend class with an eval to trap this duplicate error and ignore
> > it silently (or just warn about it) except the fact that it's
> > trying to fix something that probably sh
I've been meaning to dig into the everything2 code (which powers
perlmonks I think, amongst other things ..) and see how they do the
cross ref stuff. They seem to have a pretty nice "node" abstraction
which is the core of the problem, I think.
the membership stuff relies on a common API, I guess.
On Tue, Jul 29, 2008 at 02:21:10PM +0200, Daniel McBrearty wrote:
> 1. letting users keep existing member and login creds
> 2. being able to cross ref to other parts of the site eg. for a
> certain node, easily have a "discussion" link, and the reverse link
> from the forum
If you ever think of a
my 0.05 (possibly a bit OT) :
I looked previously at a few ways of adding forums etc to the site
using 3rd party code, indeed there are many possibilites (some perl,
some not)
The thing that was always a sticker for me was getting some kind of
logical integration, ie:
1. letting users keep exist
Quoting Nigel Metheringham <[EMAIL PROTECTED]>:
> On 29 Jul 2008, at 12:30, Tobias Kremer wrote:
> > The short time window between the find() and create() calls of the
> > find_or_create() method indeed is the problem. It sounds like this
> > window
> > should be too small to ever happen but in rea
On 29 Jul 2008, at 12:30, Tobias Kremer wrote:
The short time window between the find() and create() calls of the
find_or_create() method indeed is the problem. It sounds like this
window
should be too small to ever happen but in reality it happens very
often in our
(and other's) application
Quoting Ash Berlin <[EMAIL PROTECTED]>:
> Maybe this was mentioned in earlier in the thread, (or perhaps this is
> the problem in the first place?), but DBIx::Class does have a
> find_or_create method.
The short time window between the find() and create() calls of the
find_or_create() method indee
On 29 Jul 2008, at 11:49, Tobias Kremer wrote:
Quoting Tobias Kremer <[EMAIL PROTECTED]>:
However, I'm unsure how to detect if the error really was a
duplicate entry
error or something else.
die $@ if $@ && $@ !~ /duplicate/i;
This doesn't work because different DBs throw different errors.
Quoting Tobias Kremer <[EMAIL PROTECTED]>:
> However, I'm unsure how to detect if the error really was a duplicate entry
> error or something else.
> die $@ if $@ && $@ !~ /duplicate/i;
> This doesn't work because different DBs throw different errors.
Also, flash() is supposed to always return a
Quoting Matt S Trout <[EMAIL PROTECTED]>:
> On Mon, Jul 28, 2008 at 01:03:52PM +0200, Tobias Kremer wrote:
> > Is there anything speaking against wrapping line 52 of the DBIC backend
> > class with an eval to trap this duplicate error and ignore it silently
> > (or just warn about it) except the fa
On Mon, Jul 28, 2008 at 09:36:44PM -0700, John Beppu wrote:
> On Mon, Jul 28, 2008 at 2:40 PM, Matt S Trout <[EMAIL PROTECTED]>wrote:
>
> > On Mon, Jul 28, 2008 at 08:27:27AM -0700, John Beppu wrote:
> >
> >
> > > Imagine if you could install a blog, a wiki, a forum, or a store just as
> > > easil
12 matches
Mail list logo
