fREW Schmidt
fREW Schmidt
yeah but that stuff is "for free" if you are using DBIC; you just won't have it if... you aren't using DBIC
If anything I think DBICDH is *too* extensible.
Why are you calling deploy instead of install?
Interesting historical note: the original reason I wrote DBICDH was to have multiple schemas in one database. It supports it just fine as is and as far as I know...
Different versions; I'm not sure how they could be different schemas otherwise :)
yeah when the SQL is generated it should store it as json or yaml or something, instead of a flat file of just sql with ";\n" joining the statements.
nah the stuff in the table is just for auditing. I think you're right re the options. The one other thing to consider is legacy implementations. If you turn on...
At this point making such a change would be backwards incompatible for anyone who has depended on the existing behavior for very long. I'd accept a PR to make it...
[Use the documented interface](https://metacpan.org/pod/DBIx::Class::Helper::Row::ToJSON#TO_JSON)
Can you write a test that I can just run? You should be able to see if a $row has a compenent loaded by checking `$row->isa('DBIx::Class::Helper::SelfResultSet')`, for example.