Re: [sqlalchemy] Re: Is it good practice to copy all sqlalchemy models (tables) for every API I create?

i have a few projects families with a model like this: /shared_model/setup.py /shared_model/shared_model/ /shared_model/shared_model/sqlalchemy_api/.. /shared_model/shared_model/sqlalchemy_model/.. /shared_model/shared_model/utils/... /shared_model/tests_unit the sqlalchemy_model directory jus

Re: [sqlalchemy] Re: Is it good practice to copy all sqlalchemy models (tables) for every API I create?

As told by Jonathan, I’m trying to create a separate package for the models. Can anyone point me in the right direction to create the models as a module. I can’t seem to think how to do it because of the different ways you can connect to the database and there is the unit test to do. I just need

Re: [sqlalchemy] Re: Is it good practice to copy all sqlalchemy models (tables) for every API I create?

Thanks Jonathan. Exactly what I wanted to know. Desmond On Tue, 14 May 2019 at 02:22, Jonathan Vanasco wrote: > Are all of these APIs for the same company/organization (e.g. in-house > services), or are you developing something for different companies (you are > an agency with clients)? > > If

[sqlalchemy] Re: Is it good practice to copy all sqlalchemy models (tables) for every API I create?

Are all of these APIs for the same company/organization (e.g. in-house services), or are you developing something for different companies (you are an agency with clients)? If everything is for the same company, I typically define and maintain a single model in a dedicated separate package. The