Page 1 of 1
smartquerry read only
Posted: Tue 12 Jun 2007 09:29
by sbslavonac
After installing version 6.05, all queries are set to read only when user connect.
I can work normally but useres keep getting read only error when trying to modify records.
Has anything changed on user rigths in 6.05
Boris
Posted: Wed 13 Jun 2007 07:45
by Plash
We could not reproduce the problem. Please describe the problem more detailed. Specify the SQL text for the TSmartQuery component that is read-only, and the script to create tables used in the query.
Posted: Sat 21 Jul 2007 11:09
by sbslavonac
Plash wrote:We could not reproduce the problem. Please describe the problem more detailed. Specify the SQL text for the TSmartQuery component that is read-only, and the script to create tables used in the query.
Found what was changed.
Select statment on table with no primary key
Select rowid, t.* from test_data
and using ROWID for insert, update... switches querry to readonly if user is not shema owner
while
Select t.rowid, t.* from test_data
work normaly for all users
Posted: Mon 23 Jul 2007 07:34
by Plash
You should set the SetFieldsReadOnly option of the TSmartQuery component to False.
Posted: Mon 23 Jul 2007 08:59
by Plash
Please describe also how are you changing the current schema, and specify whether you open some queries before changing the schema. This information should help us to reproduce the problem.
Posted: Mon 23 Jul 2007 10:41
by jfudickar
In my scenario the following query is readonly
Code: Select all
SELECT V.*, ROWID
FROM SYST_PARAM_VALUE V
And this is readwrite :
Code: Select all
SELECT V.*, ROWID
FROM systools.SYST_PARAM_VALUE V
I'm connecting with a different user then systools. And SYST_PARAM_VALUE is a public synonym.
All based on 6.10.
Any ideas?
Greetings
Jens
Posted: Tue 24 Jul 2007 08:37
by Plash
We have fixed this problem. The fix will be included in the next build of ODAC.
Posted: Tue 24 Jul 2007 11:48
by jfudickar
Can you send me the fix by mail.
I have the component source.
Greetings and thanks
Jens
Posted: Tue 24 Jul 2007 12:28
by Plash
We have sent the fix to your e-mail.