By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,131 Members | 1,728 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,131 IT Pros & Developers. It's quick & easy.

one view for 2 different tables

P: n/a
Dear my friends...

I am developing a database application with postgres
7.2.x, qt on SuSE 9.1 . I am in a situation where I
have to use QDataTable and I have to use QSqlCursor
that support only 1 table manipulation ( QSqlCursor *
cursor = QSqlCursor("viewpatrix", true, db); ).

So, as a strategy I make a view. with this view I hope
I can work with more than 1 table at a time.

kv=# create view viewpatrix as select customer.custid,
customerdescription.descr
iption, customer.firstname,
customer.lastname from customer, customerdescription
where
customer.custid=customerdescription.custid;

but I have problems if I want to make data update and
data insertion from the QDataTable because I don't
know how the rule should be.

kv=# create rule viewpatrixcustdesc as on update to
viewpatrix do instead update customerdescription set
description=new.description where custid=old.custid;
CREATE RULE
kv=#

OK, it works if the user wants to update the data in
table "customerdescription".

should I simply create another rule like this:
kv=# create rule viewpatrixcust as on update to
viewpatrix do instead update customer set
firstname=new.firstname, lastname=new.lastname where
custid=old.custid;
CREATE RULE
kv=#

But how to make that the user can I also update the
data in the table "customer" (customer.firstname and
customer.lastname).

Is it possible to create one view but from
updating/inserting the data in the coresponded rule
than the records in more then 2 tables are also
updated/inserted?

Thank you very much for your help.

__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 23 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.