Whats the status of DBIx::Class

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Whats the status of DBIx::Class by syphilis (Archbishop) on Aug 24, 2024 at 12:08 UTC
Is the DBIx::Class project still alive ? It's one of the modules that will be broken by perl-5.41.3 (which will be released in a few days from now). There has been much discussion about how this will be resolved - especially in relation to DBIx::Class. Cheers, Rob	[reply]
Re^2: Whats the status of DBIx::Class (Re^4: Whats the status of DBIx::Class (deprecated package separator / reading P5P) by LanX (Saint) on Aug 24, 2024 at 14:14 UTC
> There has been much discussion about how this will be resolved Is it possible to read the whole discussion in one page? ~~I'd be interested to know if %INC hooks were suggested as work around and mean to identify broken import statements.~~ Update In hindsight, there is no use for this, if the break happens at compile time and something like `use don't` is simply rejected with a fatal error. Anyway I couldn't find out since when this feature was deprecated, seems to be enforced without grace period. Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery} UPDATES 2024-08-25 15:23 GMT appended title	[reply] [d/l]
Re^3: Whats the status of DBIx::Class by syphilis (Archbishop) on Aug 25, 2024 at 01:34 UTC
Anyway I couldn't find out since when this feature was deprecated, seems to be enforced without grace period. I see the deprecation warning in 5.40.0 and 5.38.0 (but not 5.36.0 or earlier): `D:\>perl -le "print $]; $don't = 1;" Old package separator "'" deprecated at -e line 1. 5.038000` [download] And, with warnings enabled: `D:\>perl -wle "print $]; $don't = 1;" Old package separator "'" deprecated at -e line 1. Name "don::t" used only once: possible typo at -e line 1. 5.038000` [download] Cheers, Rob	[reply] [d/l] [select]
Re^4: Whats the status of DBIx::Class (deprecated package separator) by LanX (Saint) on Aug 25, 2024 at 15:01 UTC
Re^3: Whats the status of DBIx::Class by perlfan (Parson) on Aug 24, 2024 at 16:21 UTC
There are some additional informed opinions here (reddit.com/r/perl)	[reply]
Re^4: Whats the status of DBIx::Class by LanX (Saint) on Aug 25, 2024 at 13:02 UTC
Re^5: Whats the status of DBIx::Class by NERDVANA (Priest) on Aug 26, 2024 at 08:18 UTC
Re^2: Whats the status of DBIx::Class by Anonymous Monk on Aug 24, 2024 at 12:40 UTC
Ok, thank you for that information	[reply]
Re: Whats the status of DBIx::Class by Corion (Patriarch) on Aug 24, 2024 at 10:11 UTC
While I think that using DBIx::Class (or any other ORM) is not a really good idea, others get lots of value from it. I believe the maintainer of DBIx::Class considers it feature complete and does not want to develop it further. What things do you feel are missing from DBIx::Class?	[reply]
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
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]

Update

UPDATES