Watch, Follow, &
Connect with Us

QualityCentral

Reports for: InterBase/Server/Internal  

Report Status Legend:
Open Reported Resolved Closed Withdrawn Private

Report#TitleRatingStatus
111447 Client stays connected - Parameter dummy_packet_interval
0.00 out of 5
Closed
109385 Query with two fields with the same name in two tables are executed without specify table context
0.00 out of 5
Reported
106799 Cannot empty external table using DELETE statement
0.00 out of 5
Open
104972 View Dependencies Missing and Fail
0.00 out of 5
Open
93685 Server Crash and Database totally corrupted
0.00 out of 5
Open
88241 can't find shared latch (300)
0.00 out of 5
Resolved
83446 Total Server Crash  & database corruption & destroyed
0.00 out of 5
Need Feedback
79506 (Pulled) Inner join with Stored Procedure that selects from the same table results in "No current record for fetch operation"
0.00 out of 5
Closed
77096 (Pulled) gfix -validate -full exhibits index corruption messages on table RDB$DEPENDENCIES

1. Customer says that he have rdb$dependenc
0.00 out of 5
Closed
74943 server brokes connection after select with order by varchar(512), win1251 database, collate PXW_CYRL field
0.00 out of 5
Open
66034 Query with left outer join returns wrong result
0.00 out of 5
Open
64464 Restore failure errorcode 335544333
0.00 out of 5
Resolved
64330 (Pulled) improve access method for full outer joins
0.00 out of 5
Closed
60851 Two updates and exception in procedure causes broken index
0.00 out of 5
Closed
56722 Interbase 2007 SP2 Auto Routing bug
0.00 out of 5
Open
55499 Great problem inserting a varchar variable in a blob
0.00 out of 5
Closed
51179 (Pulled) index is not used in a co-related sub select of an UPDATE statement      [CLARIFY] 602721  
0.00 out of 5
Closed
51178 (Pulled) InterBase treats SQL-89 JOINs differently than SQL-92 JOINs, leading to poor performance.   I believe the problem is in the SQL
0.00 out of 5
Open
51177 (Pulled) The Optimizer is v5.x is slowing down queries from v4.2    6/17/98 - James ===============  This is a test case for bug #8976 an
0.00 out of 5
Open
49895 Incorrect results from left outer join query in IB 2007 with SP2
5.00 out of 5
Closed
49654 (Pulled) The optimizer uses a sequential table scan to perform co-related sub-query    update actionnaire a set valeur = (select p.valeur
0.00 out of 5
Closed
47916 (Pulled) Left outer join not optimized when indexes should be used      ------------------------------------------  6/11/99 [jli]    Anot
0.00 out of 5
Closed
47603 (Pulled) CREATE/DROP JOURNAL performance is slower on Dual-Core XP than on Win2k    For example, if you perform ("CREATE JOURNAL" followe
0.00 out of 5
Closed
47602 (Pulled) Query with many joins returns "size of optimizer block exceeded"    Statement failed, SQLCODE = -904    size of optimizer block
0.00 out of 5
Closed
47599 (Pulled) Data inserted in the last transaction not seen if the database is made read only.    Workaround on existing database:  1. Make d
0.00 out of 5
Closed
47598 (Pulled) Left outer join performance without an index is terrible    This one has been around since 4.0 (at least), but has never been fi
0.00 out of 5
Closed
47437 Allow Domains to be used in Params for SP's & Triggers
0.00 out of 5
Open
44565 optimizer block exceeded
0.00 out of 5
Closed
43874 Bad query result on LEFT JOIN when multiple filters in the join
0.00 out of 5
Closed
40370 (Pulled) better error messages required for database rerouting failures    We should provide a better error when a database is circularly
0.00 out of 5
Closed
40363 (Pulled) FOREIGN KEY constraint DDL fails with multiple indices on REFERENCE key.    >>>  bug 124771 appears to be the same issue.  >>>
0.00 out of 5
Closed
39618 context already in use (BLR error) usin SELECT DISTINCT
0.00 out of 5
Need Feedback
35756 IBServer stops to respond on parallel selects: Thu Oct 26 16:40:29 CEST 2006
0.00 out of 5
Open
27525 (Pulled) Heavy index inserts causes internal gds consistency check    - InterBase V7.1 SP2 (without and with Security-Patch)  - Windows 2
0.00 out of 5
Closed
27513 (Pulled) Too many foreign keys in a single script causes a "request depth exceeded" error.
0.00 out of 5
Closed
8116 Corruption of non-uniqe indexes (SP2 applied)
0.00 out of 5
Closed
7607 Name of Referential Constraint not defined in constraints table
0.00 out of 5
Closed
7416 index keys lost due to UPDATE rollback and garbage collection
0.00 out of 5
Closed
7409 Insert into large database causes corruption of indexes as shown by gfix -v -full.
0.00 out of 5
Closed
7400 Optimizer is not picking the optimal indices in some cases.
0.00 out of 5
Closed
< Prev Next >

Server Response from: ETNACODE01

Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.