Project

General

Profile

Actions

Bug #93223

open

Wrong syntax for ALTER INDEX on PostgreSQL

Added by Jörn Wagner over 3 years ago. Updated over 1 year ago.

Status:
Accepted
Priority:
Should have
Assignee:
Category:
Database API (Doctrine DBAL)
Target version:
-
Start date:
2021-01-05
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
postgresql
Complexity:
Is Regression:
Sprint Focus:

Description

Database compare generates statements like ALTER INDEX public_index_phash_freeindexuid2_idx RENAME TO "freeIndexUid_65098221". This results in an error:

/* ERROR:  relation "public_index_phash_freeindexuid2_idx" does not exist */

The first argument needs to be quoted and case-sensitive like ALTER INDEX "public_index_phash_freeIndexUid2_idx" RENAME TO "freeIndexUid_65098221".

My PostgreSQL version is 12.5.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Epic #90719: PostgreSQL related issuesAccepted2020-03-10

Actions
Actions #1

Updated by Jörn Wagner over 3 years ago

  • TYPO3 Version changed from 11 to 10
Actions #2

Updated by Jörn Wagner over 3 years ago

  • Description updated (diff)
Actions #3

Updated by Jörn Wagner over 3 years ago

Actions #4

Updated by Stephan Großberndt about 3 years ago

  • Related to Epic #90719: PostgreSQL related issues added
Actions #5

Updated by Stefan Bürk over 1 year ago

  • Status changed from New to Accepted
  • Assignee set to Stefan Bürk

Failed to reproduce it yet for a "changed" index. However, I get similar error when a field should be renamed (to zzz_) with postgres, and can reproduce this in v10/v11 and also main/v12. Thus, interessting that this happens with doctrine/dbal 2.x and 3.x (for renaming the field).

I would guess, that it boiles down to the workaround for postgres which is in the compareing stuff which has been added as fascadeds, and eventually the same for index.

So I will take this issue as granted and will look into it again try to fixing it.

Actions

Also available in: Atom PDF