@peateasea Reading the article it looks like you need to create a PP object and then throw a resultset object at it.
Have you considered extending it that one could load it as a plugin to their resultset (base) class and call a method on any resultset object?
@demiguise One more thing: If you want to get more experience with #DBIxClass and how Coocook is using it you could also contribute a small task that involves DBIC.
We always have some issues open labelled with "good first issues" for beginners.
https://gitlab.com/coocook/coocook/-/issues?label_name[]=good%20first%20issue
In particular there’s issue #320 that’s about simply removing some old fallback which allows removing a UNIQUE constraint from the DB.
https://gitlab.com/coocook/coocook/-/issues/320
If you want to give it a try I’d be glad to help you tackle this 
@demiguise If you’re asking to “hear” something about #DBIxClass from me personally:
There’s my 14min talk about database migrations with DBIC (English slides, German talk, no English subtitles yet) from 20th German #Perl Workshop #gpw2018 online. That’s pretty much the toolset Coocook still uses today. Can’t believe this talk was already 7 years ago 
https://www.youtube.com/watch?v=iWmVlDXsKFU
@dboehmer (that’s me ) is also available for hire to do DBIC talks, trainings, consulting </advertisement> 
@demiguise I still found ORMs in other languages inferior compared to #DBIxClass. Anyway we’ve learned something since the incarnation of DBIC nearly 20 years ago. That’s why Chad Granum started DBIx-QuickORM last year. The repo hasn’t seem activity for some months now but I still hope this project will fly.
https://metacpan.org/dist/DBIx-QuickORM
@demiguise Unfortunately though the development of #DBIxClass has stalled and there even seems to be unclarity about the project’s ownership and governance. Don’t expect new releases or even further development. This is really a sad state for a framework that I consider one of #Perl’s potential USPs 
DBIC is so mature that you can still use it reliably though.
@demiguise Well, #DBIxClass has proven to be very stable and powerful. Most often I found a way to implement unusual queries in DBIC and there’s always a workaround possible by using custom #SQL if you give up.
For me the main benefit of using a powerful ORM like DBIC is that you can reuse DB code in OOP fashion. Our Coocook::Schema::Result[Set]:: namespace has many methods providing tiny bits that can be plugged together like building blocks. Plain SQL quickly becomes very repetitive …
@coocook #dbixclass is just insanely cool, I started using it within a small, hobby-fiddling Dancer2 web app.
Is there a chance to hear about your experiences using it? 
At lot has changed in the last 10 years but Coocook always has been a web application based on #Perl with #CatalystFramework and #DBIxClass. These frameworks didn’t move fast but proved to be rock solid! 
In the meantime we integrated other components like #Bootstrap and infrastructure like #GitLab with CI and #Docker for easier development (soon: also deployment). Fast moving #Javascript libraries have caused many more problems than the mature Perl ecosystem.
I seldom release modules to #CPAN mainly because there’s so much great stuff there already. An answer on StackOverflow about pretty printing DBIx::Class result sets got me thinking. I then climbed onto the shoulders of several giants to create a wee module which does just that. Introducing DBIx::Class::ResultSet::PrettyPrint!
https://peateasea.de/introducing-dbix-class-resultset-prettyprint/
Imagine this situation: I have a Mojolicious app where the unit test suite uses DBIx::Class and DBIx::Class::Fixtures. I want to run Selenium tests with Test::Mojo::Role::Selenium, but that always points at the dev DB and not at the test DB that DBIC created.
Is it possible to tell the running Mojo app to stop using the dev DB (which I don't want to pollute with test data) and instead run with the Fixtures-built test DB (and hence use transactions I can roll back)?
Is the #DBIxClass mailing list dead? I sent an email but my mail server can’t deliver the email because connections to lists.scsys.co.uk timeout …
https://lists.perl.org/list/dbix-class.html
Unfortunately the Issues tab on GitHub for DBIC is disabled
https://github.com/Perl5/DBIx-Class
@frew I am using your module DBIx::Class::Helper::ResultSet::IgnoreWantarray and just found it doesn’t make many_to_many() accessors ignore wantarray(). If you add such a relationship and call the accessor in list context you get Result objects.
Do you think the module should take of that?
The wantarray is here: https://metacpan.org/release/RIBASUSHI/DBIx-Class-0.082843/source/lib/DBIx/Class/Relationship/ManyToMany.pm#L77
I think the *$meth_name should be replaced by the *$rs_meth_name built by that code. 
@mjgardner Main developer answering here:
Backend https://metacpan.org/pod/DBIx::Class::DeploymentHandler with UI https://metacpan.org/pod/App::DH
Entry point in our codebase:
https://gitlab.com/coocook/coocook/-/blob/master/lib/Coocook/Script/Deploy.pm?ref_type=heads
It supports both SQL files and arbitrary script files. For example the 8→9 upgrade adds a column and converts a string for that column in #Perl:
https://gitlab.com/coocook/coocook/-/tree/master/share/ddl/SQLite/upgrade/8-9?ref_type=heads
I gave an introductory talk about this at the German Perl & Raku Workshop #GPW2018. YouTube English subtitles seem to be ok:
https://www.youtube.com/watch?v=iWmVlDXsKFU (13min)
#dbixclass
Why we've changed our database schema 26 times until now:
- make Coocook easier to use by simplifying required input
- add new features like organizations (groups of users)
- add missing metadata like creation timestamps
Longer gaps are difficult changes that took long to prepare:
1. add database versioning in the first place
2. drop infamous table "quantities" that connected units that can be converted, like "masses" with lb and kg, etc.
#perl #sql #SchemaVersioning #graph #dbixclass #dbi
@Perl I have a hard time getting this database query to work with DBIx::Class. I gave my best to describe it in a useful way. I’d very much appreciate any hints or questions:
