You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
My TypeORM connection is using the entityPrefix parameter to prepend characters to the database table names, so as not to confuse with other tables in the system. After moving to v3 and using the migrations approach in the database connection, new, empty tables are created without the entity prefix, as well as the private_key table.
My workaround was to hard-code the prefix on all table names in the migrations code.
To Reproduce
Steps to reproduce the behaviour:
On an existing app that was running v2 using an entityPrefix on the database connection, bump to v3 and use migrations
Observed behaviour
A new set of database tables are created, alongside the tables that have the entity prefix. Also, the private_key table is created without the entity prefix.
Expected behaviour
The entityPrefix should be prepended to all tables in the migrations files.
Versions (please complete the following information):
Veramo: 3.0
Ionic/angular/capacitor app
Node Version 14.16.1
The text was updated successfully, but these errors were encountered:
* fix(data-store): add support for db ConnectionOptions with entityPrefix
fixes#724
* chore: use different infuraProjectId in tests
* docs(core): simplify type definitions for VC/VP and link to spec
* fix: private key migration
Co-authored-by: Simonas Karuzas <[email protected]>
Bug severity
3
Describe the bug
My TypeORM connection is using the entityPrefix parameter to prepend characters to the database table names, so as not to confuse with other tables in the system. After moving to v3 and using the migrations approach in the database connection, new, empty tables are created without the entity prefix, as well as the private_key table.
My workaround was to hard-code the prefix on all table names in the migrations code.
To Reproduce
Steps to reproduce the behaviour:
Observed behaviour
A new set of database tables are created, alongside the tables that have the entity prefix. Also, the private_key table is created without the entity prefix.
Expected behaviour
The entityPrefix should be prepended to all tables in the migrations files.
Versions (please complete the following information):
The text was updated successfully, but these errors were encountered: