Skip to content
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

BUG: get_variable for postgres never returns a value. #9710

Merged
merged 1 commit into from
Nov 24, 2024

Conversation

vel21ripn
Copy link
Contributor

$this->variables[$varname] = rcube::get_instance()->config->get('db_' . $varname);
if (!isset($this->variables)) {

The first line always creates an array "variables" and because of this the server variables are never read.

Because of this, the insert_or_update() method never uses the

"INSERT INTO ... ON CONFLICT DO UPDATE SET ..."

command, and the logs constantly show errors adding records to the message cache due to "duplicate key".

 $this->variables[$varname] = rcube::get_instance()->config->get('db_' . $varname);
 if (!isset($this->variables)) {

The first line always creates an array "variables"
and because of this the server variables are never read.

Because of this, the insert_or_update() method never uses the

  "INSERT INTO ... ON CONFLICT DO UPDATE SET ..."

command, and the logs constantly show errors adding records to the message cache
due to "duplicate key".
@alecpl alecpl added this to the 1.6.10 milestone Nov 24, 2024
@alecpl alecpl merged commit 613ccd7 into roundcube:master Nov 24, 2024
16 checks passed
alecpl pushed a commit that referenced this pull request Nov 24, 2024
Because of this, the insert_or_update() method never uses the "INSERT INTO ... ON CONFLICT DO UPDATE SET ..." command, and the logs constantly show errors adding records to the message cache due to "duplicate key".
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants