Migrate database queries to SQLAlchemy #81

Open
opened 2020-02-16 19:12:00 -05:00 by JoshuaBoniface · 6 comments
JoshuaBoniface commented 2020-02-16 19:12:00 -05:00 (Migrated from git.bonifacelabs.ca)

Now that SQLAlchemy is used for database schema migrations and handling (560cb609ba et al), consider migrating all database interactions to SQLAlchemy.

From some preliminary testing, this looks like it will require some significant refactoring of the provisioner functions.

Now that SQLAlchemy is used for database schema migrations and handling (560cb609bac3efb7415e3d43ba8d0d06382c21e5 *et al*), consider migrating all database interactions to SQLAlchemy. From some preliminary testing, this looks like it will require some significant refactoring of the provisioner functions.
JoshuaBoniface commented 2020-02-25 22:57:21 -05:00 (Migrated from git.bonifacelabs.ca)

changed milestone to %4

changed milestone to %4
JoshuaBoniface commented 2020-11-08 14:32:04 -05:00 (Migrated from git.bonifacelabs.ca)

I don't think I'm going to implement this. Doing manual SQL is not that bad, and the representations of SQLAlchemy while nice are foreign enough to me to not be worth the effort. Maybe one day.

I don't think I'm going to implement this. Doing manual SQL is not that bad, and the representations of SQLAlchemy while nice are foreign enough to me to not be worth the effort. Maybe one day.
JoshuaBoniface commented 2020-11-08 14:32:06 -05:00 (Migrated from git.bonifacelabs.ca)

closed

closed
JoshuaBoniface commented 2021-06-17 02:58:55 -04:00 (Migrated from git.bonifacelabs.ca)

Worth keeping this issue around just in case.

Worth keeping this issue around just in case.
JoshuaBoniface commented 2021-06-17 02:58:56 -04:00 (Migrated from git.bonifacelabs.ca)

reopened

reopened
joshuaboniface added this to the (deleted) project 2022-10-07 23:32:24 -04:00

Moving this to the v2 project as a nice-to-have. The current manual SQL works more than well enough.

Moving this to the v2 project as a nice-to-have. The current manual SQL works more than well enough.
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: parallelvirtualcluster/pvc#81
No description provided.