Re: Whats the status of DBIx::Class

Replies are listed 'Best First'.
Re^2: Whats the status of DBIx::Class by jdporter (Paladin) on Aug 24, 2024 at 11:17 UTC
It has 130 unresolved tickets.	[reply]
Re^3: Whats the status of DBIx::Class by Tux (Canon) on Aug 25, 2024 at 08:25 UTC
IIRC many of those open issues/tickets are requests for half-baked features that are being rejected because that are out-of-scope for DBIx::Class. The developers could not get an agreement over the threshold of feature-complete and then the owner put a brake on development, which I completely understand from a burn-out perspective: you don't want to lead a team that is only in disagreement. I share Corion's view. I do not see an easy way-out of this dilemma. Enjoy, Have FUN! H.Merijn	[reply]
Re^3: Whats the status of DBIx::Class by marto (Cardinal) on Aug 25, 2024 at 09:51 UTC
In addition to what tux said, they aren't all bugs. The distinction being that rt is primarily a bug tracker not a support forum.	[reply]
Re^3: Whats the status of DBIx::Class by perlfan (Parson) on Aug 24, 2024 at 16:13 UTC
Yet people still use it. Idk how many are new users and how many are using it with existing applications; but I am of the camp with those who don't use ORMs. Some people love them, and it's not usually the people that I expect. It's only failing 1 of 240 tests as I write this. I suspect something else will come out with `class` available in core now, anyway.	[reply] [d/l]
Re^4: Whats the status of DBIx::Class by jdporter (Paladin) on Aug 26, 2024 at 13:34 UTC
The point is, it's not just about "what other features does it need?" I haven't gone through the list myself, but I have to suppose that at least some of the tickets are legit bugs. So I can totally see the OP's concern.	[reply]
Re^2: Whats the status of DBIx::Class by Anonymous Monk on Aug 24, 2024 at 11:10 UTC
Its not a case of missing functionality its more a case if its a good idea to use in a long term project	[reply]
Re^3: Whats the status of DBIx::Class by NERDVANA (Priest) on Aug 26, 2024 at 08:05 UTC
Currently the state of DBIx::Class is perfect for a long term project - it isn't changing, and it does tons of useful query generation. DBIx::Class does have some bugs in the design, and does have some misfeatures, but at this point fixing any of them would break back-compat, and the people with decades-old projects would most likely prefer that it remain stable. As an everyday user of DBIx::Class, I'd say its biggest problem is the learning curve to onboard new people. Clearly that isn't a bug that can be fixed without breaking back-compat :-) To make it nicer to use, I suggest DBIx::Class::Helper::ResultSet::Shortcut and my own DBIx::Class::ResultDDL. It's a terrific force-multiplier if you have large complex dynamic queries to write.	[reply]