Zeoslib Portal

I have logged about this in Bug tracker.

Sandeep

Hi Mark

If the table has a primary key then only we raise an exception. If the table has no primary key then there is no way to identify a record uniquely and we allow multiple records to be updated. And we could raise an exception, as you suggested, based on some setting in the query?

Sandeep

I think existing code will not break as database engines don't allow updates to computed columns.

Sandeep

Assuming one update command is executed for each record updated (in TZTable/TZQuery) the updatecount must always return 1. If the updatecount is not 1, either for wmWhereAll or wmWhereKeyOnly, then this is an error condition. If multiple records are updated then the query must have been executed dir...

Currently Zeos allows computed columns to be edited but an exception is raised as soon as the record is posted. Should computed columns be marked as read-only?

Sandeep

I think it might be alright to add a property to ZQuery.Properties, but that means it has to done for each query and cannot be done for a database connection. What if this switch is added to TZConenction.Properties? I am not quite sure about updates to multiple rows. Do you mean when used with Cache...

The update done by second session should overwrite the updates done by the first session if WhereMode is wmWhereKeyOnly, but when it is wmWhereAll the update does not succeed as the record cannot be searched based on the where clause made. This I think should raise an exception as the update has fai...

Hi Mark I have changed the way DEFAULT was removed from RDB$DEFAULT_SOURCE. function TZInterbase6DatabaseMetadata.GetColumns(const Catalog: string; const SchemaPattern: string; const TableNamePattern: string; const ColumnNamePattern: string): IZResultSet; var Key: string; SQL, Where, ColumnName, Def...

Mark what are your thoughts on this issue?

Sandeep

Zeos query returns update count which can be used to determine if the update was successful or not.

I think this should be used to tell user what has happened otherwise the user does not know if the upadtes were successful or not.

Regards

Sandeep

It's got nothing to do with FB versioning, but the way the updates are handled by Zeos are not correct(IMO).

Has anyone verified this?

Regards

Sandeep

Hi Yogi

Add "DBCommonTypes" to uses clause in the unit where you get the error.

Regards

Sandeep

Hi Yogi

Install Zeos and then look in IO folder for Zeos broker. Install that and you should be working with Zeos and IO.

Regards

Sandeep

I haven't noticed this before but I think this behavior is not correct. What is happening is I have a simple app connected to Firebird and Transaction Isolation is set to ReadCommitted. I run 2 instances of the same app and then edit same record. The first app updates the record but if I edit the sa...

Remove quotes around 321 and try.

Regards

Sandeep