Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE

Поиск
Список
Период
Сортировка
От Grzegorz Jaśkiewicz
Тема Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE
Дата
Msg-id AANLkTik73TGN9Ukh84R_2fIRYAH24EH83vM8DIo6wA0C@mail.gmail.com
обсуждение исходный текст
Ответ на Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE  (Thom Brown <thombrown@gmail.com>)
Список pgsql-general
not really, as it depends on pretty much both tables.
This is where de-normalization would actually makes sens, except for
that it wouldn't - because it will badly effect all my other queries
(joining on varchar is so slow).

I could drop FK, and replace that with my own trigger(s), but that's a
lot of mess.
Other idea, is to maintain some sort of a temp table that will hold
all names deleted, and use it. But still, not very nice nor obviuos.



--
GJ

В списке pgsql-general по дате отправления:

Предыдущее
От: Adrian Klaver
Дата:
Сообщение: Re: how to create an admin user for restore database.
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: unexpected effect of FOREIGN KEY ON CASCADE DELETE