{"_id":"@sphereon/ssi-sdk-data-store-common","_rev":"173-970749bd09c9fe74bcb697b1ce77c97e","name":"@sphereon/ssi-sdk-data-store-common","dist-tags":{"unstable":"0.9.1-unstable.20","latest":"0.9.0","next":"0.9.1-next.42"},"versions":{"0.6.1-unstable.84":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.6.1-unstable.84","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-rn:migration:generate":"npm run typeorm -- migration:generate -c migration-react-native -d src/migrations/react-native -n","typeorm-rn:migration:run":"npm run typeorm -- migration:run -c migration-react-native","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"3.1.2-next.84","@veramo/utils":"3.1.2-next.84","debug":"^4.1.1","typeorm":"0.2.45"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.5.2"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"d4b7207bc5a97e97841c9236b8dad1b6cb6bfafb","description":"


\"Sphereon\"
Data Store (Typescript)
\n

\n
\n \"Sphereon\"\n
Data Store (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage entities based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store (Typescript)
\n

\n
\n \"Sphereon\"\n
Data Store (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage entities based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store (Typescript)
\n

\n
\n \"Sphereon\"\n
Data Store (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage entities based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store (Typescript)
\n

\n
\n \"Sphereon\"\n
Data Store (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage entities based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store (Typescript)
\n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data storage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript)


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript)


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the index.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.8.1-unstable.272","_nodeVersion":"16.19.1","_npmVersion":"lerna/4.0.0/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-l7kgX5wlvWYuubETsp9d5HFaqCCgC8LxVvJWO56WXFVp4clTjqnDdXUb9Ih3YzYExBoQt3foLno1jbTNADVTsw==","shasum":"cdbc89561be08bba731deae1e46848249d36e367","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.8.1-unstable.272.tgz","fileCount":84,"unpackedSize":133068,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCNYyUXY89R4E0qRi9Rp9g2jcFQa+fOBrDyeQflN4VeDQIgcCZt7AhGLDrYITvw+/6FgW6fgUfXZLh4I/24YIkIrYU="}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkBgJSACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqkHA//ZQ/9T4IyIQGfQ596d2URdz9Mbf+qYUwTlYUlTtDaFm3j2QhP\r\np3mkApiNf5WkTy+xzcErbkM15/j9LaVLQQfwHw5SDFtz+C/OO5jJEj8KdrGx\r\ngKAs96fx9wIgadw6T+SKdfhzD+kJQtWINx4zg28Sv10rCqtwzgfh8T+ZI3iI\r\noOKvhmrY2GdLfISEx3+CO1k4eQ+OzScKiOU5BlsJA9suetLL5ByNbXqdr7bF\r\n65lv/JQ434nvpCBH4FshYe/qO2YCvBihZY/IelBqGLn2k+M1mE/vZVeU/whp\r\ntt06pjAxbvsPFfNSB828QV+bbmY2ogNIPtgJXSEX20qWucckNNmEbWhmagbi\r\nxMbdQ087h3TPLXDioEkw3kHB47PCGqhiD9+tLtco5Dn9BCmkOxN4Algn3iiH\r\nlcnn7NVg2gQSRf1s/z6VuR8AmeVkA/r8Jofzt97Y2+QoZCJHVI3VOynFzE6L\r\ni9zKMIgl8BFx2xEikqdEYau9AMpGTdZrx9wFTQAHJXwuSeYE4JPqScTRP8pq\r\nwAP/JNvnZbJPnkRdkmW1fsPS3uLS5hijy7yPK/gjGti5vL0eRuedMRVITBu6\r\nWdxehRX7G9UqGP5lL5kiQJIpBf2kr7gru/RZu2kUkQ8kWit3E/MMykR4Sdkn\r\nBZSZOxRbHGaFsFWTMEwSTU91gjishZxow2Y=\r\n=egSB\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.8.1-unstable.272_1678115410435_0.3168724014609161"},"_hasShrinkwrap":false},"0.8.1-unstable.277":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.8.1-unstable.277","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build --clean && tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.10"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.6.4"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"9f18a4df8f65c5fc9fb23591404af2ab19b90a76","readme":"\r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.8.1-unstable.277","_nodeVersion":"18.14.2","_npmVersion":"lerna/4.0.0/node@v18.14.2+x64 (linux)","dist":{"integrity":"sha512-3v+tihTpu7be+BYZC7OceGUElVyuo+aWGONd02ZjMTcKT2eY95q4nBN8fwMvM+t7hU47HfuexxMll0BSlr1+Sg==","shasum":"41cc138159d72923741027d7e7ad02056c484692","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.8.1-unstable.277.tgz","fileCount":84,"unpackedSize":133068,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIQCPOLeUbs536Zl3S2qlZqa9A16iH2TZ5rXjPR6L3qufRwIgS9tQk9eBdZhS+uFPU8DolrlsQpe/iirVE1P2YAQELGo="}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkByd9ACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmrvqA/+PXoN4JI6VA8BsSPuUjPFZIwPDS8Cff37xnlcGlEXf6XfIYuL\r\nkJi2iMn6N3ceabPrfIot4ZhztKpLXiVZsQh2Or+9gqoX0YA7zwMoPCu5TbgE\r\nxycmh0uK8lYuQTyX4xCJCoFdPxQ2TAGpH31d+i1Xy++RiGoLIDYE41oDX+2O\r\nVJXAwJqXInAhD42WiLb1fMzadSrla5WBSgMzQk89LRlM6AIjwhUeOu/wZ4lN\r\nv8K4aYOLBMDkp7pySaWXkFIxWcmCptyTbImjpEeCJ0qOcU2A27bsQflFTGhf\r\n+5DOraz1FNzZmbu8gxgPWS5PKmYCrqRrL+/ew1O7U7PWKKrXntt+FlHg5u6x\r\nqmQgJ7a7ChKfFWBfu5kl2aiqsUDeRPUxw4DBDw4Gh0mzTNidWJUOulUpCvuJ\r\ncCPj6h3KFQL3gNJK6TSuBvEXzOrJLA78wq1tsQ8jyLunsrqwTwEZV5a0Z9TC\r\nEt1eyXPrqVLzOBEIqUSXx6NFz9dxPUCjpxht4ulYhgOrPAMTZfOc+6U/tbXO\r\nlzy1MQXOUPyK72JMyxGGS5UZzpY6hILA+G2af6rSGYAgtBH9kSmlSpYoiLNA\r\nfsZcRV1XxyjzsqN4h9QsIRnbrNtaPQ3mU5NZ9KQnB7CcuIh4qitWFuXW8C9s\r\n4+5fsDQsdE4N1TaImmIwaQN//Wwoo+ABrg8=\r\n=qhYU\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.8.1-unstable.277_1678190461146_0.5365998979860509"},"_hasShrinkwrap":false},"0.8.1-unstable.266":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.8.1-unstable.266","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.10"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.6.4"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"f089ac18dc470f0b8c581b49e70e7eba64d72bc3","readme":"\n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.8.1-unstable.278","_nodeVersion":"16.19.1","_npmVersion":"lerna/4.0.0/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-Zn3BSXxyfubqjUSc7ZHU1M2MIR9KVPqaSyBqcKqijC5nuvDKcK8if9XqZ+w+6X4c9yGesO7o1GcqW/osCQXrUQ==","shasum":"7a8204c5995e6384a54b41b0b4a77829ac89af41","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.8.1-unstable.278.tgz","fileCount":84,"unpackedSize":133068,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCHrZEFpZs8ADGZ3SlRkw247Ju7Z53W1WYEj4HPT9LQgQIhANpywuK3JH6DqaeTIbFcVUGfrdJ+hojCbrLYsznvChd6"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkCLekACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmpgkBAAkQ/UCWMENJux9E2QEqZRQUJW+U8Ua3UrzMELi+V86TWfUkvB\r\nTe6FbQx31yQmkhCQkgAJRYmpBCQKpjfvoPS+W1PX9ZqUPqU5Gg+pxiPnsIl1\r\nkkbVhCPVgrvKIlQPHAdWKpmLMlGHoA75UiCuxNEXhIVJSICdWcwzBpwuwcsF\r\nyR6x5SPY8/eJUU09ij3jpwVNlQexv5lrx5j9EdWkvpavBBe/rV4dr+GguK9F\r\nYYa+Jl42ILcdEfJYx3Oo0ZFmRx18DJ6abQMw0P7Ao5JlnfK/ZaxIabn/+veY\r\nNlB8XY/viaawW8b0SIaNcZw2x/KTQ7SIuuv8ruKiTHNllyi0W1cJaCSEC/D1\r\nrtdtV43Yxp9mERXXD/8tVU9odC+Fiv+yVFuOOS64ySGmQzXX2C+FRp/1johB\r\nBz1bD8qUJsrsOHrBlPLuhU4Wb4uDDPaGRFYRG2lr5sWpmOQD0FedfH+IO5N0\r\nsRGPeSlZe20GsKIUgL2XMopYBoE9I5z6pXfxjj3Mj7m59pjdWAlK7K8kb/KM\r\nq9D6CjDcX7GbVG7NdzqnvmP9oncUlNUmt9wPFvY4AEe5DbYFkHJCKk14VNCg\r\nl1Yq7t6zMM7scruG21RnXbE5EwRXU3dRQ0r5E1+btA33ys9aVMFOt8F03Lqg\r\nVk+MedpXrHugphV+NEdYnmMoszuncgmYFNc=\r\n=AeM7\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.8.1-unstable.278_1678292900300_0.09164667615952138"},"_hasShrinkwrap":false},"0.8.1-unstable.279":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.8.1-unstable.279","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build --clean && tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.10"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.6.4"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"31f0db4b692262cab82cfda3d038589f1987fc69","readme":"\r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.8.1-unstable.279","_nodeVersion":"16.19.1","_npmVersion":"lerna/4.0.0/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-tfgyCvJ6eZC3qdij+b8SqIfZ+L8EoWufRx6q2q1zVSvkEXZdaKHkUBgYzRfVR7uQjy6lwknJMgHd8YpxhIPReA==","shasum":"d772308ecc9722a6e393bee930f59b9cf3502571","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.8.1-unstable.279.tgz","fileCount":84,"unpackedSize":133068,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQD8sjsa1pEKgCgJ+9ZJkUzkfjUY64UMJkWDrzW4pNYySwIhAM5VauLp/IPVeUD7268wtdIIBD0uoeYZRUkVpWRThwOs"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkCOXoACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmoUkA//Udgx0hUaNkPLUR+ktB1dcxI3OT64RjdOldgdCunhWL4o78Rz\r\niYr20k8m/RiojhS7g6DsbzbFmGoNWT3gxqGIt006Vq1UVoqCKdpfMVIiioKe\r\nV0v70wRZiwPwTRS8GLMCX91imSr4dH+MbtTZqHoQI/dSh/MPN3eplD/VcCDi\r\nhvcba9vPYyP9rD2Bh/Ym7EFolPNlWOW97w/ZIUTVCf4YAmZINpvBdFss5D5b\r\nnJcJM4HRE/0MsDpdlEtKY254XLoIG437ESkZjLfx2+NZe+EgNitnaR7LW+Sk\r\nkoGwIObUz2wPyFwsc/87ljnc3FpGrPXiwM29xy8/ROUPfjfMRT/ISXDNJwFz\r\n8Af7LnCDuJhARzzDn4PmfVtsvs2Rcmv/ehWnwxgQm/f4B1tTU237veIPVbq5\r\nhc6UqG3xb+zyvPTBmek8Q1rOp6t1ubMzinMyVdv6iPzr5sah4G5u4vANv/bc\r\nR2hh4tV05yywXdcmmxWV700lW8yAvzV83hWI4qTxFALhAl5ZUFuLgPqIIRVm\r\nBlXBcYg5VyrHiMFrY5jEk4CkkNfLi02ItHSZGbC82hcgWp+/1JRE0Z9i2Am5\r\n6iBn9NcYSwN/Z0/N005paF0eNjQP0XqtcfWjX0bboWNWJX2zFfDUPT0m04vI\r\nI/tM5HXgLD+8geypqyzbc3a7LIOsKERC7qU=\r\n=j3rC\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.8.1-unstable.279_1678304744123_0.2999129979851245"},"_hasShrinkwrap":false},"0.8.1-unstable.280":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.8.1-unstable.280","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build --clean && tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.10"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.6.4"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"fb79036acd60a5da2aaab44b49fc942436d3b23e","readme":"\r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.8.1-unstable.280","_nodeVersion":"16.19.1","_npmVersion":"lerna/4.0.0/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-B4ukSFNH6mJ8Os0Bc34tkKS90+x34cvIJXTPw/PvY4oAXL2Wh9/vusmZQk+wh5pFUD3CurGxCdHGzdubT60ljw==","shasum":"a1888b344b57e6ee48400018bada2754b694e84c","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.8.1-unstable.280.tgz","fileCount":84,"unpackedSize":133068,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQDarjIHOVkfQx6XXrqcmUXTuPr+CSJP6vhBNYvl5doieAIhANOBWHtdjnHC9B/BuQJB5Xz/OxM0bwEnrb8bQucvudZ1"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkCQgqACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2Vmqr6A/+KSChGbI46D4pp63FntlPLFp5x2S0pOOL3o8ACTKMTPf3x6lw\r\nYr8vES+xk59YN/87nLF5jzdHqfy5VDXD7I2KZRR9p77kK4CASVUu1TnOf+7p\r\noZeVkjs0HV0G0YQKkT0DXVaSgUUdGWVww0b0zMAnQTzRieF/h4yV1/28f9wH\r\n+Rt2h3x06zwm7pSXxNspVsD0VgNFttfLpofRK67z2gxbOUociiorcHQAPRG4\r\nGq+cb9DPWls4XDAWEXkyMGAFzefQy9dsDbv0P0xS7PC7Rg5veHELNbEkz7q8\r\nWNL7ikRD+3o8vKbDINak/WGKmlSjcqREBcpZZ0DWy2fnIXOIdiAVEaCqJ2nh\r\nvpD8zHzRIv4NTGlY2EiNYPJNlbrVXa0zq/nwgsAPJhHDZY9xvTR+TjjXsf+3\r\n6kvMVgyuqFIRvgF51cJXyKpZUGjSfJyoqdQD/bVBcPot4tO3hRkzSptQrf7M\r\nvJxrRN9GIsZmpqYrm3uMMQhYyI2krJ1e5RAA+FvXIAHevvhEzHaVWtGmjciI\r\nkkiyOBtF7HoQMhr/gzzoPpFxYNgwqRNUqiYzwINNAhr+STYGp4cWqmmabrrp\r\njOfbCScRac042E8A5nz5ixR/l2d1lFFDgQ1Fh1tCa8xgpyC8ysXbRxXyxlNq\r\nir8TeAOO72vXF3HjyfOlj7VVGpweNyYgM/8=\r\n=Q0xK\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.8.1-unstable.280_1678313513907_0.6138609347172876"},"_hasShrinkwrap":false},"0.8.1-next.272":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.8.1-next.272","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.10"},"devDependencies":{"@types/debug":"4.1.7","ts-node":"^10.9.1","typescript":"^4.6.4"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"a34f653b26d26b6d980aa9196b814ad42cfa5e3f","readme":"\n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript)


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.9.1-unstable.27","_nodeVersion":"16.19.1","_npmVersion":"lerna/6.5.1/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-4yphbt63BZ+swbBGfJsOzxoaKr7cjNAamcMzS5DMD9qNa0qqXE4Z8WqIfoiS8PvFeQAJJYXDBRo3YzsInlkUhg==","shasum":"eaebd9e510d71c3ef5f777faf1ecfa7a3b9a0a66","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.9.1-unstable.27.tgz","fileCount":84,"unpackedSize":132818,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEYCIQCvd7dvvCtigjSeylX1FQz91OM1P2ODxj5bBFcEj/jV/AIhAPaQXw3Hag+ERhfiRSDFJqiB856lsyA8PzozuR5vazDp"}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkEc9qACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmogMw/5Ad+xVnGgp+DW4IhvzZTSLVkLviosTVf/LmodHBrxyMTbToyx\r\nTv/qezF6Vd2xsEKRTnxBpEjBjzBME2891aJcAYRtJ5uIWVvFqa6FwsUixm4Z\r\nXsqOYo5ZkKead8cdNWsjDKPxnyPt4eZtKSn8kTC1zxpwqSb3M3Ymt1k1Agej\r\n9RIcqaDGWuL3O8l3hb31mZy9C/2T9aBCx7kBjg5ZGoWhQ+Csxf/B/1e+BItH\r\neMqS3uad8n/F5sLZN2aZAgL94W7O5dWc1kRhjzsJ52th3DZARRu2STaH7F9D\r\n4JFXDk95xi4LZKhRUtaUhhk1woJXrOBeCtFLvU6kfdi7Tkfd+haYKUEtrEWp\r\nbWpwDUZVabpDF9dSyqrifyr9lfBozZxVVqdyqlRzaEoAh0wWbFm+W6Bf1VD9\r\nM1VT3qqo2e7hxImcVCwo+9OfIGhfoYHB8L3f2ZW6d0OxHzc8mYz+m6raeW8N\r\n+scQnfMc+ip3JJ2R5HEqoDC4gjMt/6o9+A/GIMucSqekfJoWrXAUJYfQoKbB\r\nbvLBn3rNjSdZ0ZNkfEYaYA+VNvpLgo2bkVq9mYBTYgjP6kdn5jriVxgotkpg\r\nm+k9b6tJRrh3Gg52eSkAX2UPE5n9lrAfTQcDcZM6llUB95KWrv/ohK90FzJd\r\njo8H7cZiy1NC0wM2NO+Rb6MeR4daTo+rf88=\r\n=XDLH\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.9.1-unstable.27_1678888810578_0.09348693475736969"},"_hasShrinkwrap":false},"0.9.1-unstable.28":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.9.1-unstable.28","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.12"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"9ec78ec4fba4ce80a35d1e9577aceb8adc10d726","readme":"\n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \r\n

\r\n
\r\n \"Sphereon\"\r\n
Data Store Common (Typescript) \r\n
\r\n

\r\n\r\n---\r\n\r\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\r\n\r\n---\r\n\r\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\r\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\r\n\r\n## Installation\r\n\r\n```shell\r\nyarn add @sphereon/ssi-sdk-data-store-common\r\n```\r\n\r\n## Build\r\n\r\n```shell\r\nyarn build\r\n```\r\n\r\n## Module developers\r\n\r\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\r\ninformation from entities, ensure that migration files are being created to reflect the updates.\r\n\r\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\r\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\r\n\r\n### Create a migration file\r\n\r\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\r\n- Make a copy of that database so you can always easily go back\r\n- Run the respective commands for postgresl and/or sqlite:\r\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\r\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\r\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\r\n NameOfYourMigration_\r\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\r\n migrations entrypoint from their TypeORM config.\r\n- If you wish to check whether applying the migration works you can execute the respective\r\n\r\n### Applying migrations\r\n\r\nThere is an example sqlite file in the root called migration.sqlite.\r\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\r\nchanging an entity,\r\n\r\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\r\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\r\n\r\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\r\n","readmeFilename":"README.md","description":"\r

\r
\r \"Sphereon\"\r
Data Store Common (Typescript) \r","bugs":{"url":"https://github.com/Sphereon-Opensource/SSI-SDK/issues"},"homepage":"https://github.com/Sphereon-Opensource/SSI-SDK#readme","_id":"@sphereon/ssi-sdk-data-store-common@0.9.1-unstable.30","_nodeVersion":"16.19.1","_npmVersion":"lerna/6.5.1/node@v16.19.1+x64 (linux)","dist":{"integrity":"sha512-L1yHeUFwlf3RA748nPrg22Yx594Emu0GFC8Dn4LP8azlCFnQIRT3y8OL5Yrvf3h1REblp8mHgSVG6bBv39aixA==","shasum":"7658ecd922582f02a16a407483c16bae5b9297b6","tarball":"https://registry.npmjs.org/@sphereon/ssi-sdk-data-store-common/-/ssi-sdk-data-store-common-0.9.1-unstable.30.tgz","fileCount":84,"unpackedSize":132957,"signatures":[{"keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA","sig":"MEUCIBw3yJSYSxKxIkEF5b61XJuN9FbzIFLXD2pMDjmA84qlAiEAoNKzhMGuBxdycy16HYaiSkCcklICp2rxBt2kL8f/Jvg="}],"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v4.10.10\r\nComment: https://openpgpjs.org\r\n\r\nwsFzBAEBCAAGBQJkEd2yACEJED1NWxICdlZqFiEECWMYAoorWMhJKdjhPU1b\r\nEgJ2VmqCJg//RDYv578gV0wPLiUrDDhUDHfd6nROEnkKpMcEW37Vd4PCC1t0\r\nM/0+8wzebW9MSiz5M9aZAqVYhIBkZKc64DP0+Jis4VP0KF5z5DskcTuI0mo7\r\nskd5x/R6qN5a5k5yHkiZ7NQgYES0I86jM1M31ChKs7+qS8CxnGoomKYCqDM4\r\nHAy2xCRoYWfrSgaRy1O6OXAduEObbbScYaLjDaO8mda7ZHURRdo6vnUaxjel\r\nR7xMoU5JVcdVAZCAkKDacWzOKJQezpaEdHIqV1gU7w3ywLiXHEp42VU96g3x\r\n8Dae+twCS++Czl1Cv3TxrF/U/njMg0NOTYkSZpQMkiCjfGy3NfLkQawiN0Im\r\nckGm10SBna3zkq8PwFKgQUCeib/frpJYICgp5oHDuntQJBALNjT1uxYNbJ9h\r\nIn9hg1bFSwCIRliMBbIxeQRlvvi4DOSKkmj22lnQCfy+LeviKRElneiHoLAT\r\nv8hNK3O93lAUaaoFLnjHgBFuUEtoSSC4519w2j3M3DWR8jhLg7Aw7urllCwY\r\nccXbmq9xqDHHGCNjCSKBoBKHOrljufsbmc3lNcNXYvz+YuU0MeqfsLGe6Jxw\r\nzLFb5PDtEZq7Y6Oi459btlffB956AQ9LEYOQWZa/YunUbL8d2U2qM+cnK95H\r\nyeg6tbR6m3ueS54Qx/U0Xk6pmQOlmHFVQmo=\r\n=Sbo8\r\n-----END PGP SIGNATURE-----\r\n"},"_npmUser":{"name":"nklomp78","email":"dev@sphereon.com"},"directories":{},"maintainers":[{"name":"nklomp78","email":"dev@sphereon.com"},{"name":"nklomp","email":"nklomp@sphereon.com"},{"name":"spostma","email":"spostma@sphereon.com"},{"name":"bramtencate","email":"btencate@sphereon.com"}],"_npmOperationalInternal":{"host":"s3://npm-registry-packages","tmp":"tmp/ssi-sdk-data-store-common_0.9.1-unstable.30_1678892466331_0.13582016231282878"},"_hasShrinkwrap":false},"0.9.1-unstable.34":{"name":"@sphereon/ssi-sdk-data-store-common","version":"0.9.1-unstable.34","source":"src/index.ts","main":"dist/index.js","types":"dist/index.d.ts","scripts":{"build":"tsc --build --clean && tsc --build","typeorm":"ts-node --project ./tsconfig.json -r tsconfig-paths/register ../../node_modules/typeorm/cli.js --config src/migrations/internal-migrations-ormconfig.ts","typeorm-sqlite:migration:generate":"npm run typeorm -- migration:generate -c migration-sqlite -d src/migrations/sqlite -n","typeorm-sqlite:migration:run":"npm run typeorm -- migration:run -c migration-sqlite","typeorm-postgres:migration:generate":"npm run typeorm -- migration:generate -c migration-postgres -d src/migrations/postgres -n","typeorm-postgres:migration:run":"npm run typeorm -- migration:run -c migration-postgres"},"dependencies":{"@veramo/core":"4.2.0","@veramo/utils":"4.2.0","debug":"^4.3.4","typeorm":"^0.3.12"},"publishConfig":{"access":"public"},"repository":{"type":"git","url":"git+ssh://git@github.com/Sphereon-Opensource/SSI-SDK.git"},"author":{"name":"Sphereon","email":"dev@sphereon.com"},"license":"Apache-2.0","keywords":["TypeORM","SQLite","PostgreSQL","Connection Store"],"gitHead":"0a44ee76d7df4f0a1bd0a7aa092ab1f417269f97","readme":"\n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript) \n

\n
\n \"Sphereon\"\n
Data Store Common (Typescript) \n
\n

\n\n---\n\n**Warning: This package still is in very early development. Breaking changes without notice will happen at this point!**\n\n---\n\nSSI-SDK data storage common entities and interfaces based on TypeORM. This package provides entities that relate to data\nstorage. Please note they need to be used with the @sphereon/data-store and @sphereon/connection-manager packages\n\n## Installation\n\n```shell\nyarn add @sphereon/ssi-sdk-data-store-common\n```\n\n## Build\n\n```shell\nyarn build\n```\n\n## Module developers\n\nWe use TypeORM migrations to support database changes over time. As soon as you need to update, add or delete\ninformation from entities, ensure that migration files are being created to reflect the updates.\n\nCurrently we support migrations for sqlite databases, typically used during development and on mobile platforms. Next to\nthat we also support Postgres. Obviously you need to have a Postgresql database at hand when working with Postgres.\n\n### Create a migration file\n\n- Ensure you have an existing sqlite/postgres database at hand with the old situation\n- Make a copy of that database so you can always easily go back\n- Run the respective commands for postgresl and/or sqlite:\n - `yarn run typeorm-postgres:migration:generate NameOfYourMigration`\n - `yarn run typeorm-sqlite:migration:generate NameOfYourMigration`\n- Check in the src/migrations folders to find a file in the respective sqlite/postgres folder which contains _\n NameOfYourMigration_\n- Update the credential-mapper.ts file in the respective directory to include the migration. Users will import that file as their\n migrations entrypoint from their TypeORM config.\n- If you wish to check whether applying the migration works you can execute the respective\n\n### Applying migrations\n\nThere is an example sqlite file in the root called migration.sqlite.\nWe use the sqlite file to keep track of changes we made and to ensure there are no incidental changes by a developer\nchanging an entity,\n\nThis file is kept up to date by applying the command: `yarn typeorm-sqlite:migration:run`\nThe same can be done for a local Postgres database using the command `\"typeorm-postgres:migration:run\"`\n\nYou can look at package.json or https://typeorm.io/migrations to apply migrations to your own database(s)\n","readmeFilename":"README.md","description":"


\"Sphereon\"
Data Store Common (Typescript)


\"Sphereon\"
Data Store Common (Typescript)