> In your first query, ADDCACHE was set to false. Does the problem exist
> in both cases?
Definitely.
> Just guessing:
> • Did you get any errors reported while performing updates?
No.
> • Do you have any symbolic links (and potential circular dependencies)
> in the directory you are parsing?
In your first query, ADDCACHE was set to false. Does the problem exist
in both cases?
> It seems safe to delete those temporary databases regularly, then?
Absolutely.
Just guessing:
• Did you get any errors reported while performing updates?
• Do you have any symbolic links (and potential circul
> It looks as if databases are not cleaned up in your environment that
> are temporarily created during the update step.
>
> I guess it will be difficult for you to get this reproduced for us?
Indeed.
It does happen on Windows and Linux, though. I pretty much run the default
setup.
This is a c
Hi Daniel,
It looks as if databases are not cleaned up in your environment that
are temporarily created during the update step.
I guess it will be difficult for you to get this reproduced for us?
Best,
Christian
> DBNAME_2618234251
>
> caused by
>
> db:replace($dbname, $dbpath|| '/' || $fname
Hi,
sometimes in my update operations BaseX deliberately is spawning several
databases like the following, with a name of the database plus underscore and
number:
DBNAME_2618234251
caused by
db:replace($dbname, $dbpath|| '/' || $fname, $file-to-import, map {
'intparse': true(),
5 matches
Mail list logo
