Re: Application Design and PostgreSQL
От | Janning Vygen |
---|---|
Тема | Re: Application Design and PostgreSQL |
Дата | |
Msg-id | 0107172008370B.17343@janning обсуждение исходный текст |
Ответ на | Application Design and PostgreSQL (Janning Vygen <vygen@planwerk6.de>) |
Список | pgsql-general |
Hi Thanks for your very detailed answer. but i am still not sure about few points Am Dienstag, 17. Juli 2001 19:03 schrieb Chad R. Larson: > On Tue, Jul 17, 2001 at 12:59:09PM +0200, Janning Vygen wrote: > > But then i thought: Do i really need complex middleware or is it > > just a wrapper around PostgreSQL?? > > The middleware is the part that is particularly custom to your > world. It should be written as portably as possible, for example > Java Servlets in a container such as Tomcat (free) or JRun (not > free). > > The communication to the database engine should be only ANSI SQL > via ODBC or JDBC. ok i got your point. vendor independency is great! > > I think its possible to implement the whole logic inside > > postgresql. > > Perhaps. And if your application is for internal use only, and you > never imagine selling a license version to anyone, and you'll never > get into the ASP business with your app, go for it. but first whats the hype about object orientaded databases? Why do i need them? and second. what happens if you have a custom application with a database backend and you still have a frontend like pgsql? A customer wants to have a html based formular for their customers to insert rows into the tables and still wants to access this databse via MS Access or other tools. If i have all logic inside the database i dont need a middleware to prevent the data from getting corrupted via other tools. wouldnt it be fine to have all logic inside the database and i can use my object orientaded wrapper or a frontend like pgsql or something else. It seems to me that it would make more sense if all logic is inside the databse because i can prevent my data from being corrupted. AND: What happens if i change a type from int2 to int4 inside the databse. i still have to maintain the middleware. So i always have to keep two things up to date. There will always be some logic inside the database at least something like types. Is your opinion to put mostly every business logic inside the middleware just because the object orientated approach inside databases isnt standarized yet? thanks a lot again for your very detailed answers. It was a great help! janning -- Planwerk 6 /websolutions Herzogstra�e 86 40215 D�sseldorf fon 0211-6015919 fax 0211-6015917 http://www.planwerk6.de
В списке pgsql-general по дате отправления: