8000 The value of CL-POSTGRES::PARAMETERS is 2327607654652096140, which is not of type LIST · Issue #115 · fukamachi/mito · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

The value of CL-POSTGRES::PARAMETERS is 2327607654652096140, which is not of type LIST #115

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
svetlyak40wt opened this issue Sep 13, 2022 · 1 comment

Comments

@svetlyak40wt
Copy link
Contributor

MITO.DB.POSTGRES:ACQUIRE-ADVISORY-LOCK function signals this error when I try to apply migrations.

Probably that is because this function passes parameter as is instead of list:

(defun acquire-advisory-lock (conn id)
  (dbi:do-sql conn "SELECT pg_advisory_lock(?)" id)
  (values))

In this commit CL-DBI's DO-SQL was changed to accept parameters as lists.

After I've changed these functions like this, migration was applied successfully:

(defun acquire-advisory-lock (conn id)
  (dbi:do-sql conn "SELECT pg_advisory_lock(?)" (list id))
  (values))

(defun release-advisory-lock (conn id)
  (dbi:do-sql conn "SELECT pg_advisory_unlock(?)" (list id))
  (values))

Environment

Mito on fcc8003 commit (latest for now).

CL-DBI was installed from Ultralisp.org. Release number 20210831151553.

svetlyak40wt added a commit to svetlyak40wt/mito that referenced this issue Sep 18, 2022
Also pg_advisory_lock call was updated for the latest cl-dbi.
This closes issue fukamachi#115
@svetlyak40wt
Copy link
Contributor Author

This issue is fixed in the pull: #118

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant
0