[
http://tracker.firebirdsql.org/browse/CORE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vlad Khorsun reopened CORE-405:
-------------------------------
Assignee: Vlad Khorsun
> Garbage vs indices/constraints
> ------------------------------
>
> Key: CORE-405
> URL: http://tracker.firebirdsql.org/browse/CORE-405
> Project: Firebird Core
> Issue Type: Bug
> Components: Engine
> Reporter: Dmitry Yemanov
> Assignee: Vlad Khorsun
>
> SFID: 744175#
> Submitted By: dimitr
> If an index contains garbage and automatic GC
> is disabled, then it's impossible to create unique
> indices or PK/UK/FK constraints.
> For example:
> 1) attach with isc_dpb_no_garbage_collect
> 2) insert some duplicate data
> INSERT INTO T1 (F1) VALUES (1);
> INSERT INTO T1 (F1) VALUES (1);
> 3) delete these rows
> DELETE FROM T1;
> 4) create unique index
> CREATE UNIQUE INDEX IDX1 ON T1 (F1);
> You'll see "attempt to store duplicate value ..."
> error message, which is incorrect in this case.
> Since indices work outside transaction control, it
> may be a initial design/implementation pitfall. It
> appears the index creation and partner lookup
> code never touches records and hence is unable
> to determine which versions are actual at the
> moment of index creation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
