+1
___
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN: http://dev.catalyst.perl.org/repos/bast/DBIx-Class/
Searchable Archive: http://www.grokbase.com/group/dbix-class@lists.scsys.co.uk
More options are always better and the acrimony over a win-win
situation is more telling than anything else that’s been said.
___
List: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/dbix-class
IRC: irc.perl.org#dbix-class
SVN:
+1 for the fork. It's the only way to eat our cake and have it;
affording different lines of development and culture without friction
and strife.
Since very few, if any, of you were here at the beginning, you
probably don't know that this is essentially how DBIx::Class was born;
as an indirect
On Sun, Oct 23, 2016 at 4:19 PM, Andrew Beverley wrote:
> On Wed, 5 Oct 2016 04:07:04 -0400 David Golden wrote:
> [...]
>> * DBIx::Class (DBIC) – Peter's work provides a capstone, with only bug
>> fixes thereafter
>> * DBIx::Class2 (DBIC2) – new feature
On Tue, Oct 18, 2016 at 2:28 PM, John Stoffel wrote:
> I'm just amused by all the verbiage flowing by, but no code, cries for
> help with the code, etc. If it's all such a pain in the ass, just
> free what's here and fork the project. Sheesh... that's the open
> source way.
This starts to feel like a corporate process that will be tuned out by
what little community participates. Will more than two or three users
engage with this? Will they follow the code closely enough to have a
valid opinion?
As far as stability goes, I'd like to see—actually, I'd like to insist
I did say MST RFC:MUST be respected. :P This is only here because of
you. I was an early CDBI user and was there for the fights over its
direction and saw you as the voice of reason, patience, and vision.
Regardless of work done since, I see you as the owner. I was unaware
there was as much of a
RIBASUSHI has given this codebase a tremendous amount of care,
improvement, and deft effort. I am a user and evangelist of DBIC since
it was the first fork of CDBI that started to solve so many problems.
Peter has solved many problems since.
My view: MST must be respected but I personally defer
On Sat, Aug 20, 2011 at 8:03 PM, Rob Kinyon rob.kin...@gmail.com wrote:
It'd be nice if DBIC would convert the accessors to read-only. I think
that's the point.
In addition to the ++ for the idea I gave before I'll give a recent
story: I needed this for a current project and instead ended up
On Wed, Aug 10, 2011 at 3:05 PM, Ben Tilly bti...@gmail.com wrote:
Often database schemas have tables that should not be changed at
runtime in the application. It would be convenient to be able to mark
this fact in the class. However to avoid accidents you wind up having
to override methods
On Wed, Jul 6, 2011 at 7:01 AM, Dave Howorth dhowo...@mrc-lmb.cam.ac.uk wrote:
I have a DBIC class made up using a UNION, something like this
simplified example:
__PACKAGE__-table('nodes');
__PACKAGE__-result_source_instance-is_virtual(1);
On Tue, May 10, 2011 at 1:05 PM, Moritz Lenz mor...@faui2k3.org wrote:
does anybody know how to contact Ian Docherty, CPAN id ICYDEE?
I'd like to contact him about patches to DBIx::Class::Tree::NestedSet,
but his domain doesn't accept any emails, and alternative email
addresses I found are on
On Fri, Oct 15, 2010 at 1:18 AM, Peter Rabbitson rabbit+d...@rabbit.us wrote:
I want to make sure I am getting this right - are you proposing that
we discuss drastically changing a stable API, potentially breaking
DBIC for hundreds if not thousands of users, all for the sake of
correctness? I
On Wed, Aug 4, 2010 at 7:50 AM, fREW Schmidt fri...@gmail.com wrote:
I note you use the term 'ascendants' which is not a real word and so would
be confusing. Is this the same as 'ancestors'? If so then it would be best
to use ancestors since that is a word know by other people and it keeps it
I really like Loader but there are things that are impossible (I
think) to do with it; specifically, using the UTF8Columns component
(since it's per column).
I found a nice article, in Japanese, on how to make your model base
handle utf8 (in what I believe is the same fashion UTF8Columns
15 matches
Mail list logo