Closed salieri closed 1 year ago
This looks good. Similar work is happening here: https://github.com/mde/model/pull/151 Would it be possible for y'all to coordinate to make sure this stuff plays nicely together?
By the looks of it, for a successful merge all that's needed is for me to go over the tableizeModelName() calls and make sure they use tableizeModelNameFull() instead where appropriate. Should not be a problem at all.
I think to make things a little more seemless is to just change the _tablelizedModelName function just like I did in #151. In that function you can check to see if a schema is defined or not. But it should be first merged with #151 and then the schema support added.
Where are we on this? Can y'all get this sorted out, or do I need to do separate merges and then sort it out?
Will get back to you after crunch mode is over, give it a few weeks.
Excellent. :) Lemme know if there's anything I can do to help.
In larger applications, data is often divided between schemas and databases.
This change allows developers to define schema and database for each model that uses Postgres or MySQL database adapters. (Schemas only supported on Postgres.)
Interface is simple -- when defining a model, just add "db" and/or "schema" values: