Change Details

//As a Wikisource Export developer, it would be preferred if our database used Doctrine ORM to be consistent with Symfony standards and allow for easier management of the schema.// **Background:** Currently WS Export is using it's [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | own system ]] to create and update the database (which only logs exports at the moment). While not strictly necessary, it is better to move to [[ https://symfony.com/doc/current/doctrine.html | Doctrine ORM ]], complete with [[ https://symfony.com/doc/current/doctrine.html#migrations-creating-the-database-tables-schema | migrations ]], to stay more consistent with Symfony standards and more easily allow us to make changes to the schema. This would be especially beneficial if/when we tackle the job queue (T253283). Finally, having our querying go through Doctrine will allow for easier caching if/when we migrate the phetools queries to WS Export (T257886). **Acceptance criteria:** * Convert the existing [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | CreationLog ]] class to use Doctrine ORM * Querying itself does not necessarily need to use [[ https://symfony.com/doc/current/doctrine.html#querying-with-the-query-builder | query builder ]] but it could.

//As a Wikisource Export developer, it would be preferred if our database used Doctrine ORM to be consistent with Symfony standards and allow for easier management of the schema.// **Background:** Currently WS Export is using it's [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | own system ]] to create and update the database (which only logs exports at the moment). While not strictly necessary, it is better to move to [[ https://symfony.com/doc/current/doctrine.html | Doctrine ORM ]], complete with [[ https://symfony.com/doc/current/doctrine.html#migrations-creating-the-database-tables-schema | migrations ]], to stay more consistent with Symfony standards and more easily allow us to make changes to the schema. This would be especially beneficial if/when we tackle the job queue (T253283). Finally, having our querying go through Doctrine will allow for easier caching if/when we migrate the phetools queries to WS Export (T257886). **Acceptance criteria:** * Convert the existing [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | CreationLog ]] class to use Doctrine ORM * Querying itself does not necessarily need to use the [[ https://symfony.com/doc/current/doctrine.html#querying-with-the-query-builder | query builder ]] but it could.

//As a Wikisource Export developer, it would be preferred if our database used Doctrine ORM to be consistent with Symfony standards and allow for easier management of the schema.// **Background:** Currently WS Export is using it's [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | own system ]] to create and update the database (which only logs exports at the moment). While not strictly necessary, it is better to move to [[ https://symfony.com/doc/current/doctrine.html | Doctrine ORM ]], complete with [[ https://symfony.com/doc/current/doctrine.html#migrations-creating-the-database-tables-schema | migrations ]], to stay more consistent with Symfony standards and more easily allow us to make changes to the schema. This would be especially beneficial if/when we tackle the job queue (T253283). Finally, having our querying go through Doctrine will allow for easier caching if/when we migrate the phetools queries to WS Export (T257886). **Acceptance criteria:** * Convert the existing [[ https://github.com/wsexport/tool/blob/master/src/CreationLog.php | CreationLog ]] class to use Doctrine ORM * Querying itself does not necessarily need to use the [[ https://symfony.com/doc/current/doctrine.html#querying-with-the-query-builder | query builder ]] but it could.