You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be an option to specify a custom timestamp in migration creation,
for example, when somebody manages his own migrations and wants the same timestamp for multiple schemas.
The Solution
An option in the CLI to specify a custom timestamp when creating / generating a migration.
Considered Alternatives
Changing the file's name after creation manually...
Additional Context
Relevant Database Driver(s)
DB Type
Relevant
aurora-data-api
no
aurora-data-api-pg
no
better-sqlite3
no
cockroachdb
no
cordova
no
expo
no
mongodb
no
mysql
no
nativescript
no
oracle
no
postgres
no
react-native
no
sap
no
sqlite
no
sqlite-abstract
no
sqljs
no
sqlserver
no
Are you willing to resolve this issue by submitting a Pull Request?
✅ Yes, I have the time, and I know how to start.
✖️ Yes, I have the time, but I don't know how to start. I would need guidance.
✖️ No, I don’t have the time, but I can support (using donations) development.
✖️ No, I don’t have the time and I’m okay to wait for the community / maintainers to resolve this issue.
The text was updated successfully, but these errors were encountered:
docs: added description for the option
An option in the CLI to specify a custom timestamp when creating or generating a migration.
Closes: typeorm#8500
* feat: add custom timestamp option in migration creation
An option in the CLI to specify a custom timestamp when creating or generating a migration.
Closes: #8500
* feat: add custom timestamp option in migration creation
docs: added description for the option
An option in the CLI to specify a custom timestamp when creating or generating a migration.
Closes: #8500
Feature Description
The Problem
There should be an option to specify a custom timestamp in migration creation,
for example, when somebody manages his own migrations and wants the same timestamp for multiple schemas.
The Solution
An option in the CLI to specify a custom timestamp when creating / generating a migration.
Considered Alternatives
Changing the file's name after creation manually...
Additional Context
Relevant Database Driver(s)
aurora-data-api
aurora-data-api-pg
better-sqlite3
cockroachdb
cordova
expo
mongodb
mysql
nativescript
oracle
postgres
react-native
sap
sqlite
sqlite-abstract
sqljs
sqlserver
Are you willing to resolve this issue by submitting a Pull Request?
The text was updated successfully, but these errors were encountered: