-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
PostgreSQL load indexes without column ordering #16639
Comments
Why does it matter? |
From the perspective of the database, of course the order of the columns in the index is very important. Personally, my special case, I have a package to simplify the work with migrations, there is a function to delete the index by columns, without specifying a name. We can assume that these are my problems, but if such a method already exists, then I think that it should be carried out exactly as I suppose. _С точки зрения базы данных, разумеется порядок колонок в индексе очень важен. Лично мой частный случай, у меня есть пакет для упрощения работы с миграциями, там есть фукнция удаления индекса по колонкам, без указания имени. Можно считать, что это мои проблемы, но если уже существует такой метод, то я думаю, что он должен выполнятся именно так, как я предполагаю._ |
OK. |
I don't understand how we can get the index creation time. Suspect it is impossible. As result there isn't way to range indexes according their creation sequence. |
The function \yii\db\pgsql\Schema::loadTableIndexes returns all table indexes, but without the original column sequence
Функция \yii\db\pgsql\Schema::loadTableIndexes возвращает все индексы таблицы, но без изначальной последовательности столбцов
What steps will reproduce the problem?
We create a migration with 2 indices on the same columns, but with different order
Создаем миграцию с 2мя индексами на одни и те же столбцы, но с разной очередностью
What is the expected result?
What do you get instead?
Additional info
The text was updated successfully, but these errors were encountered: