andrew wrote:
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Andrew,
In one particular table there are, what appear to be deleted records
that do
not show in a dataview window.
They are not returned if one just queries the single table.
But if one uses that table in a join, then they records are returned.
...
Strange - never heard of this, never encountered this myself. No idea
what could cause this.
If this problem is reproducible with the database you got, and the
sender allows you to publish it - please submit an issue. The Java
versions used to create/access the DB might be interesting ...
Ciao
Frank
Well, it turns out there is already a database available to you that
has this problem. The one referenced in Issue 69995.
Tt appears the issue is actually something different from what is
stated, it is not the cont in the navigator bar that is in error, it
is the dataview result set.
After looking at the database from the other day, It struck me that
this sounded familiar after all. A SELECT COUNT value differed from
the number of records displayed in the GUI. The baseball stat's database.
Sure enough it is the same problem - actually, perhaps not exactly the
same but very similar.
When the table is opened in a data view there are only 10,080 records
reported. As I stated in the bug report, a COUNT returns 123,944 The
data in that table was downloaded from another system, the PK field
was part of the data transfer. I had always known that there where
gaps in the numbers, but ASSUMED, this was correct. Well, turns out it
isn't.
On screen for instance there is no record with the PK of 2.
But if I run a query and set a criteria of 2 for the PK field. There
it is.
I then ran a query, using a different field for the value criteria
contained in this record, again the record is returned.
Finaly just a query of SELECT * returns 123,922 records - and as it
turns out there are no gaps apparently in the PK values.
This is where it is different from the other day. The other day the
records where not returned with a select * query. But doing this today
against that same database they are returned. They still do not show
up in the dataview window however and the only change here is that I
installed OOG680m_2 yesterday.
Should I change the summary on the current Issue or close that one and
open another?
Drew
Drew, I've recently run into a similar situation with a database I'm
developing for work.
There are two tables which I import records into from a csv file via
Calc. I delete the previous records from each table prior to the import
(actually append, since the structure doesn't change) of new records.
I noticed if I deleted all the records and there were no records visible
in table view, that the size of the .odb file didn't shrink. In this
case, the .odb file is 12mb with no records, just two table definitions,
4 queries, and 2 forms defined. A seemingly empty db.
I extracted the database/data file from the odb and found that the
records (or at least the old data) was still in the database/data file.
Seems to act like DOS/Windows - when something is deleted, it's not
really deleted, just marked as deleted.
I tried copying each of the tables, definition only, and deleting the
old tables thinking this would purge the old data. It's still there.
I haven't had a chance to look, but it seems there should be some method
to 'compact' the database tables.
Marc Blakely
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
