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
Support custom schema and table name for version tracking. This is specially helpful for databases maintaining multiple schemas and requires some compliance to naming patterns and segmentation of tables. For example, instead of keeping the tracking table into [dbo].[__YuniqlDbVersions] it should be possible to keep this in [utils].[SchemaHistory]
The text was updated successfully, but these errors were encountered:
SETX YUNIQL_CONNECTION_STRING "Server=localhost,1400;Database=yuniqldb1;User Id=SA;Password=P@ssw0rd!"yuniql run -a --schema "my_schema"yuniql info --schema "my_schema"
Run with custom version history table
SETX YUNIQL_CONNECTION_STRING "Server=localhost,1400;Database=yuniqldb2;User Id=SA;Password=P@ssw0rd!"yuniql run -a --table "my_version_history"yuniql info --table "my_version_history"
Run with custom schema and version history table
SETX YUNIQL_CONNECTION_STRING "Server=localhost,1400;Database=yuniqldb3;User Id=SA;Password=P@ssw0rd!"yuniql run -a --schema "my_schema" --table "my_version_history"yuniql info --schema "my_schema" --table "my_version_history"
Support custom schema and table name for version tracking. This is specially helpful for databases maintaining multiple schemas and requires some compliance to naming patterns and segmentation of tables. For example, instead of keeping the tracking table into
[dbo].[__YuniqlDbVersions]
it should be possible to keep this in[utils].[SchemaHistory]
The text was updated successfully, but these errors were encountered: