Subject | Internal GDS software consistency... |
---|---|
Author | Marcos Vinicius Dufloth |
Post date | 2001-07-17T17:53:19Z |
Hi list.
This was extracted from borland.com: one of bug fixes in Interbase 5.6:
*---
Update failure with unique key constraint could
corrupt a database. Similar behavior to bug
#60135 with different error:
Statement failed, SQLCODE = -902
internal gds software consistency check
(wrong record length (183))
---*
So, I ask: What is the causes of corruption database further (sorry if further isn't the right word) those relates to diferent machines architectures and database copies and non-transportable backups? Would be some bug to be fixed?
Dufloth.
[Non-text portions of this message have been removed]
This was extracted from borland.com: one of bug fixes in Interbase 5.6:
*---
Update failure with unique key constraint could
corrupt a database. Similar behavior to bug
#60135 with different error:
Statement failed, SQLCODE = -902
internal gds software consistency check
(wrong record length (183))
---*
So, I ask: What is the causes of corruption database further (sorry if further isn't the right word) those relates to diferent machines architectures and database copies and non-transportable backups? Would be some bug to be fixed?
Dufloth.
[Non-text portions of this message have been removed]