hotfix
gitea/salix/pipeline/pr-master This commit looks good Details

This commit is contained in:
Pako Natek 2024-04-27 13:09:15 +02:00
parent 9e87b055b7
commit 9aa6e3f80a
3 changed files with 4 additions and 4 deletions

View File

@ -31,7 +31,7 @@ BEGIN
CALL collection_get(vUserFk); CALL collection_get(vUserFk);
SELECT (pc.maxNotReadyCollections - COUNT(*)) <= 0, SELECT (pc.maxNotReadyCollections - COUNT(*)) <= 0,
pc.collection_assign_lockname pc.collectionAssignLockname
INTO vHasTooMuchCollections, INTO vHasTooMuchCollections,
vLockName vLockName
FROM tCollection FROM tCollection

View File

@ -64,7 +64,7 @@ BEGIN
o.trainFk, o.trainFk,
o.linesLimit, o.linesLimit,
o.volumeLimit, o.volumeLimit,
pc.collection_new_lockname pc.collectionNewLockname
INTO vMaxTickets, INTO vMaxTickets,
vHasUniqueCollectionTime, vHasUniqueCollectionTime,
vWorkerCode, vWorkerCode,

View File

@ -1,5 +1,5 @@
-- Place your SQL code here -- Place your SQL code here
ALTER TABLE vn.productionConfig ADD collection_new_lockname varchar(100) ALTER TABLE vn.productionConfig ADD collectionNewLockname varchar(100)
DEFAULT 'collection_new' NOT NULL COMMENT 'Lockname value for proc vn.collection_new'; DEFAULT 'collection_new' NOT NULL COMMENT 'Lockname value for proc vn.collection_new';
ALTER TABLE vn.productionConfig ADD collection_assign_lockname varchar(100) ALTER TABLE vn.productionConfig ADD collectionAssignLockname varchar(100)
DEFAULT 'collection_assign' NULL COMMENT 'Lockname value for proc vn.collection_new'; DEFAULT 'collection_assign' NULL COMMENT 'Lockname value for proc vn.collection_new';