Re: Why does an ON SELECT rule have to be named "_RETURN"?
В списке pgsql-general по дате отправления:
| От | Tony Caduto |
|---|---|
| Тема | Re: Why does an ON SELECT rule have to be named "_RETURN"? |
| Дата | |
| Msg-id | 43EFEAEC.9050402@amsoftwaredesign.com обсуждение исходный текст |
| Ответ на | Why does an ON SELECT rule have to be named "_RETURN"? ("Ken Winter" <ken@sunward.org>) |
| Список | pgsql-general |
Ken, Why don't you tell us why you need updateable views? What exactly are you trying to accomplish? (you may have already mentioned it,but I must have missed it :-) Why don't you create a set returning function and then have the client do the updating? i.e. have another function to update the data when the client changes the data. Maybe this is not that easy for a web interface, but in Delphi or Lazarus using the tdataset it's a piece of cake. Also what about using a .net disconnected dataset? I can honestly say I have never had the need for a updatable view in any application I have ever created (thin or fat client). Maybe you just need to look at alternative application designs that don't need a updatable view. Thanks, -- Tony Caduto AM Software Design Home of PG Lightning Admin for Postgresql http://www.amsoftwaredesign.com
В списке pgsql-general по дате отправления:
Сайт использует файлы cookie для корректной работы и повышения удобства. Нажимая кнопку «Принять» или продолжая пользоваться сайтом, вы соглашаетесь на их использование в соответствии с Политикой в отношении обработки cookie ООО «ППГ», в том числе на передачу данных из файлов cookie сторонним статистическим и рекламным службам. Вы можете управлять настройками cookie через параметры вашего браузера