[dba-issues] [Issue 96716] writing to a writeable Pos tgreSQL view does not work
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96716 --- Additional comments from hjak...@openoffice.org Sun Jun 14 14:28:42 + 2009 --- Please note that I wrote if the view has been set up by a knowledgeable person. Yes, if you just set up a view without a rule it won't be writable. But since it is very easy for any PostgreSQL administrator to make certain views writable and certain views with Oracle are writable without any special treatment, it is still WRONG that OOo Base as a front end interferes and denies writing to a writable view. If a view is actually not writable, which is also very common, OOo Base should just take the error message from the database system and forward it to the user. Anything else is bad behaviour. - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 96716] writing to a writeable Pos tgreSQL view does not work
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96716
User simonaw changed the following:
What|Old value |New value
Ever confirmed| |1
Status|UNCONFIRMED |NEW
Issue type|DEFECT|ENHANCEMENT
--- Additional comments from simo...@openoffice.org Sat Jun 13 16:51:29
+ 2009 ---
Checked to see if PostgreSQL itself (natively) can insert into views what is
*NOT* the case. If I am wrong please feel free to correct me.
This is what I did:
demo=# \d packages
Table public.packages
Column | Type | Modifiers
--++---
id | bigint | not null default
nextval('packages_id_seq'::regclass)
name | character varying(100) |
version | character varying(20) |
url | character varying(200) |
licenses | character varying(50) |
groups | character varying(100) |
size | numeric|
idate| date |
descr| text |
demo=# create view vw_testqa as SELECT packages.id,packages.name from packages
LIMIT 10;
demo=# insert into vw_testqa (name) values ('asdasdasd asd');
ERROR: cannot insert into a view
HINT: You need an unconditional ON INSERT DO INSTEAD rule.
I am not an expert on how the rule system works and neither do I know how
difficult it'd be to implement that in the OOo PSQL driver.
Setting to ENHANC
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org
For additional commands, e-mail: issues-h...@dba.openoffice.org
-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 96716] writing to a writeable Pos tgreSQL view does not work
To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=96716 User simonaw changed the following: What|Old value |New value CC|''|'simonaw' - Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification - To unsubscribe, e-mail: issues-unsubscr...@dba.openoffice.org For additional commands, e-mail: issues-h...@dba.openoffice.org - To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
[dba-issues] [Issue 96716] writing to a writeable Pos tgreSQL view does not work
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=96716
Issue #|96716
Summary|writing to a writeable PostgreSQL view does not work
Component|Database access
Version|OOo 2.4.1
Platform|All
URL|
OS/Version|All
Status|UNCONFIRMED
Status whiteboard|
Keywords|
Resolution|
Issue type|DEFECT
Priority|P3
Subcomponent|none
Assigned to|dbaneedsconfirm
Reported by|hjakobs
--- Additional comments from [EMAIL PROTECTED] Sat Nov 29 20:59:59 +
2008 ---
I clearly understand that writing to views - as opposed to tables - can lead to
difficulties and that OOo cannot easily solve these. If a query involving
several tables has been created within OOo it's ok that they are not writeable
because it is impossible to tell which of the joined table the data should go
to.
BUT: If a database offers views which are easily writeable because the issue was
solved on the database side by including rules on how to deal with the
situation, OOo Base should not stop the users from taking advantage from this
feature.
Views defined in PostgreSQL (or in Oracle, for that matter) show as tables in
OOo Base, but have a different icon (containing an arrow). Please refrain from
taking the information that this is a view as a hint that this table is not
writeable. The database will complain if it cannot write to it, but it is quite
likely that it will work fine if the view has been set up by a knowledgeable
person.
I connected PostgreSQL via JDBC org.postgresql.Driver to OOo Base.
Thank you in advance for understanding the problem. I am sure the person this
issue will be addressed to is in the position to find the position in the big
heap of code where it says
if (table_type == view) { deny writing }
and just delete this little piece of bad code from our beloved OOo.
Ust let the database do its job!
-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
