Currently you cannot use the reserved token YUNIQL_DB_NAME in scripts like this:
Use [${YUNIQL_DB_NAME}]
because Yuniql doesn't replace it in scripts.
The result is that you have to introduce a token of your own for DB name, such as DBNAME, and specify it with -k during yuniql run, e.g.:
yuniql run -a -c ""Server=localhost,1433;User Id=use;Password=pwd;Database=MyDb;" -k "DBNAME=MyDb"
As you can see, not only do you have to introduce an extra token, you have to specify the DB name twice in the command, once in the connection string and once with -k. This is awkward and in fact creates potential for mistakes.
Can you please make Yuniql replace YUNIQL_DB_NAME in scripts as well? It will make the above problem go away.
Currently you cannot use the reserved token
YUNIQL_DB_NAME
in scripts like this:because Yuniql doesn't replace it in scripts.
The result is that you have to introduce a token of your own for DB name, such as
DBNAME
, and specify it with-k
duringyuniql run
, e.g.:As you can see, not only do you have to introduce an extra token, you have to specify the DB name twice in the command, once in the connection string and once with
-k
. This is awkward and in fact creates potential for mistakes.Can you please make Yuniql replace
YUNIQL_DB_NAME
in scripts as well? It will make the above problem go away.