6.10.1.10: Field's readonly flag issue.
Posted: Tue 07 Aug 2007 12:56
Hi Folks,
It seems like this has gone back and forth a bit, but I still don't see things working properly in the new release. I'm using TSmartQuery with settings:
And I see problems with the readonly flag in queries that include '*' and don't include ROWID.
This is just one example of the problem and I don't quite understand what is going on because if you use SYSDATE as the first field in the above examples they will both be properly marked readonly. Shouldn't it just be checking the updatetable's field names and setting any field that doesn't match read only? Alternately, could you surface a function that we could call to set any fields that don't match the update table's columns as read only?
Thanks for any help!
-Mark
It seems like this has gone back and forth a bit, but I still don't see things working properly in the new release. I'm using TSmartQuery with settings:
Code: Select all
Query.LockMode := lmLockImmediate;
Query.Options.FullRefresh := True;
Query.Options.DeferredLobRead := True;
Query.Options.CacheLobs := True;
Query.Options.RawAsString := False;
Query.Options.QuoteNames := True;
Query.Options.SetFieldsReadOnly := True;
Query.Options.FieldsOrigin := False;
Query.Options.RequiredFields := False;
Query.Options.DefaultValues := False;
Query.Options.ExtendedFieldsInfo := True;
Query.Options.StrictUpdate := True;
Query.Options.TrimFixedChar := True;
Query.Options.LongStrings := True;
Code: Select all
CREATE TABLE EDIT_TEST (
ID NUMBER(38) PRIMARY KEY,
TXT VARCHAR2(4000));
INSERT INTO EDIT_TEST VALUES (1, 'TESTING_1');
INSERT INTO EDIT_TEST VALUES (2, 'TESTING_2');
INSERT INTO EDIT_TEST VALUES (3, 'TESTING_3');
COMMIT;
SELECT ID + 100 "RO", ID, TXT FROM EDIT_TEST;
The first field is correctly marked as readonly.
SELECT ID + 100 "RO", ET.* FROM EDIT_TEST ET;
The first field is not marked as readonly.
Thanks for any help!
-Mark