-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jean-Claude Wippler wrote:
| Pat,
|
|> The problem is that out of 56 _B subviews all but one are as
|> expected. However, one block is damaged. The values for the date and
|> size columns have got swapped about.
|
|
| If the data file is wrong, but readable, then my first hunch would be  a
| bug.  Setting the wrong column could point to a property cache bug,
| either in the core or in the Tcl binding (the latter is more likely,
IMO).

I guess I should have specified -- I'm actually using metakit via C++
here. We have a module that provides a Microsoft COM IStorage interface
that uses a meakit virtual filesystem as the backend.

[snip]
| Did you restructure the view at any point in time?  I.e. did the  layout
| change once you started adding the first data?

No. I've only every done that on my development machine and this was
generated by one of our testers.

|
| If you can create a test set which fails (big if, I know), then I  could
| investigate or write a Python test to see whether this is Tcl-
| specific.  You can probably leave out the contents to create a much
| smaller test set.

Thats going to be tricky. So far our guys have about 100 such files up
to around 1GB in size. I scanned their tree on the server and this is
the only file with a problem -- but I know that their normal procedure
is to collect the file on the local drive and then put in onto the
server before they do further manipulation of the data.

| I can't rule out anything at this stage, but would not expect an SMB
| mount to cause problems which only alter the column choice of data
| items, I'd expect it to create an unreadable datafile by messing up
| things at a much lower level: one or more disk blocks in the file.
|
| Much larger datasets than yours, and with lots of blocked views, have
| been in use for some time.
| So my first suspicion goes to the Tcl wrapper (blocked views from Tcl
| have not been used much).
|
| Oh wait - *are* you using Tcl?  I'm jumping to conclusions a bit too
| quickly...

I guess I'm going to have to try to create another one then. I wish I
knew how they did it. :(

Pat Thoyts
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)

iQCVAwUBQqh/0GB90JXwhOSJAQJGoAP/WMt5ExByx1FNub+87EOonL+fSk0+owBz
fUQjonPRzcRIauH4+ZuuPsEwz3w+gGyg1TtrxFgKZc9Wsc7wmoTdPU/1k3twyucC
TCGFzSZvNAodZ9Fx8b8nnl/QnL5cXcPnzWGVIn/CZRzw8nsz6s1+qPSXc8KEE4L5
g/SC2E469gg=
=5lXT
-----END PGP SIGNATURE-----
_____________________________________________
Metakit mailing list  -  [email protected]
http://www.equi4.com/mailman/listinfo/metakit

Reply via email to