Re: Possible feature?
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Possible feature? |
| Дата | |
| Msg-id | Pine.LNX.4.30.0107111724300.679-100000@peter.localdomain обсуждение исходный текст |
| Ответ на | Possible feature? (Mike Mascari <mascarm@mascari.com>) |
| Ответы |
Re: Possible feature?
|
| Список | pgsql-hackers |
Mike Mascari writes: > MESSAGE ON INDEX i_employees IS > 'An employee with a matching Social Security number already exists'; > > Then, when the UNIQUE constraint of the index is violated, instead of > the message: > > 'Cannot insert a duplicate key into a unique index i_test1' > > the client application would receive: > > 'An employee with a matching Social Security number already exists' I think what you're after is TRY BEGIN INSERT ... END CATCH SQLCODE 12345 -- made up BEGIN RAISE 'your message here' END I'm positive people would kill for that kind of feature. -- Peter Eisentraut peter_e@gmx.net http://funkturm.homeip.net/~peter
В списке pgsql-hackers по дате отправления: