pgsql v. Access pt Duex: the view
От | jim davis |
---|---|
Тема | pgsql v. Access pt Duex: the view |
Дата | |
Msg-id | 3C236D3B.B1F7AEFD@amphi.com обсуждение исходный текст |
Список | pgsql-interfaces |
Ok, first thank you all who helped me with my last problem of trying to get M$ Access to query and update a PostgreSQL database. As, I am sure it is rather evident, I am somewhat new to PostgreSQL (I played with the "other" SQL DB) I reasoned that if I could get Access to update tables directly with no problems, and if all a VIEW is is just a table based on a set of queries... (you see, I'm thinking here!) I dug in and found that with the help of a RULE it became possible to UPDATE, INSERT, and DELETE from a view! So I played and, on the command line in 'psql', all worked fine. I made three little test tables, made a view that SELECTed a few choice items from each, and was able to UPDATE any column I wanted. (or that I had a RULE for). I tested it with just one UPDATE rule for my VIEW in Access, and... IT WORKED! I was able to update the VIEW! My hopes were high! So I found out that I could slap () around a bunch of UPDATEs so I could end up UPDATing all three test tables from the VIEW. But then I went back to Access... I found that Access would only UPDATE the LAST in the list of UPDATEs in the RULE and it would give me messages that "someone else was in the porcess of updating this table, try again later" if I tryed to UPDATE a column that was not the last column in the RULE list... Am I making sense? Has anyone else tried this? Am I close to my answer? My other thought was to make a function, but that's new to me too... For those new to my plight, I am trying to migrate an Access database to PostgreSQL (That is NOT the problem), but the users are all used to making the queries in Access and making reports and such. I am trying to make it as painless and as seamless for them as possiable. They are used to being able to make a query based on many tables, and being able to update the database directly from the result of the query. I have learned that most real RDBMS do not, and should not, work that way. So... That brings me back to this post. :) -- -Jim Davis Network Coordinator II Amphitheater Public Schools Voice: (520)696-5222 Fax: (520)696-5070 e-mail: jdavis@amphi.com
В списке pgsql-interfaces по дате отправления: