Re: [basex-talk] after upgrading one big disaster

Never mind. I got my program working again with the newer basex via - {local:K($y)/name} + {local:K($y)/*:name} - {local:K($y)/o/*} + {local:K($y)/*:o/*} ___ BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.un

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

> My temporary workaround is to set HTTPPATH to /, which avoids the issue. What OS do you use? My current assumption is that this is a Linux-/Mac-related issue. I've once more updated the code base and the snapshot. If the problem persists, I'll do some tests on a different system. ___

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

My temporary workaround is to set HTTPPATH to /, which avoids the issue. On 03/16/2012 05:00 PM, Charles Duffy wrote: The subject line of this thread isn't actually consistent with the behavior I'm seeing from the current snapshot -- I wonder how much time could have been saved if I'd been payin

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

The subject line of this thread isn't actually consistent with the behavior I'm seeing from the current snapshot -- I wonder how much time could have been saved if I'd been paying more attention earlier: Running the current snapshot with a default configuration, the behavior I actually see is

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

Weird - still can't reproduce this here (your query correctly returns "4" on my machine). Has anyone else tried this? Thanks in advance, Christian ___ On Fri, Mar 16, 2012 at 8:05 PM, Charles Duffy wrote: > I'm able to reproduce this with the "ns-test" module, first given

Re: [basex-talk] Use of unsalted password hashes

I agree that plain md5 hashes are not state-of-the-art anymore (..well, for quite a while). If we update our storage, however, we should guarantee backwards-compatibility. If anyone wants to dive into this.. Code patches are welcome.. ;) ___ On Fri, Mar 16, 2012 at 8:59 PM

Re: [basex-talk] Setting the context item via the native protocol

The context() method has been added. Moreover, I have added new bind() and context() function signatures to the client APIs with an additional "type" argument. Looking forward to your first tests, Christian PS: the "latest snapshots" are currently uploaded; it usually takes around 5 minutes until

Re: [basex-talk] Use of unsalted password hashes

On Mar 16, 2012, at 12:59 , Charles Duffy wrote: [...] > I'm a bit concerned about storing password hashes unsalted -- compared to a > salted hash, this makes a stolen database easier to retrieve user passwords > from, dangerous if users use their passwords for other purposes as well. > > Would

[basex-talk] Use of unsalted password hashes

Howdy -- I'm a bit concerned about storing password hashes unsalted -- compared to a salted hash, this makes a stolen database easier to retrieve user passwords from, dangerous if users use their passwords for other purposes as well. Would salting (and perhaps stretching) the hashes be consi

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

I'm able to reproduce this with the "ns-test" module, first given in my post at http://permalink.gmane.org/gmane.text.xml.basex.talk/235 (and now attached). $ basex-query 'repo:install("/home/cduffy/ns-test.xar")' $ basex-query -

Re: [basex-talk] Setting the context item via the native protocol

> Context.current() accepts only Nodes, which are database-backed; > QueryProcessor.context(), by contrast, can accept the ItemCache returned by > a query which doesn't return a database reference. > > As such -- it seems to me that what is needed is an extension to the query > command protocol (as

Re: [basex-talk] after upgrading one big disaster

Thanks for your efforts. Still, it looks as if I'd quite some time to get your example running (I'd like to, but many other todos are waiting as well). Could you send me a plain xquery file that demonstrates the varying output for 7.1 and the latest version? ___ > wget http

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

Sounds serious; but I didn't manage to reproduce this locally. Does your module import yet another module? Could you try to build an example that demonstrates the problem? On Fri, Mar 16, 2012 at 7:19 PM, Charles Duffy wrote: > On 03/16/2012 01:13 PM, Charles Duffy wrote: >> >> In my .basex file

Re: [basex-talk] REPOPATH prefixed twice on current snapshots?

On 03/16/2012 01:13 PM, Charles Duffy wrote: In my .basex file: REPOPATH = /home/cduffy/local/opt/basex-data/repo ...and running repo:list() shows my local package, with namespace http://dyfis.net/ as installed, but trying to use anything from it leads to an error similar to the following: rel

[basex-talk] REPOPATH prefixed twice on current snapshots?

In my .basex file: REPOPATH = /home/cduffy/local/opt/basex-data/repo ...and running repo:list() shows my local package, with namespace http://dyfis.net/ as installed, but trying to use anything from it leads to an error similar to the following: releng.db.basex.rest.RemoteException: [XQST005

Re: [basex-talk] Any way to persist OutputStream in DiskData?

Hi Dave, > I had played around with the AUTOFLUSH option and did notice some > improvement, which is great for my own uses when appropriate. If that option > is set to false, how often does the database actually get flushed? Only on > close? Yes. The number of flushes will be reduced as much a

Re: [basex-talk] fulltext index: case sensitive vs. case insensitive

Dear Cerstin, > Which would mean creating actually four indices to allow for fuzzy search or > exact matches as well: > > w/ stemming and w/ case sensitive > w/ stemming and w/o case sensitive > w/o stemming and w/ case sensitive > w/o stemming and w/o case sensitve. > > That's quite a lot of data

Re: [basex-talk] Setting the context item via the native protocol

On 03/16/2012 11:06 AM, Charles Duffy wrote: On 03/14/2012 07:44 PM, Charles Duffy wrote: Howdy -- Right now, I'm aware of two ways to set the context item via the native protocol: (1) Insert a "declare context item" header into the document - Disadvantage: Should only work when XQUERY3 is tr

Re: [basex-talk] Delete attributes

Thanks When I first typed it, it just started without showing any progress other than the OS busy cursor. After a couple of minutes I assumed that I had made a typo. It took 37 minutes. /William [cid:image001.png@01CC745B.AFAA47C0] Wiliam P. Heise Software Developer williamhe...@deltek.com

Re: [basex-talk] Setting the context item via the native protocol

On 03/14/2012 07:44 PM, Charles Duffy wrote: Howdy -- Right now, I'm aware of two ways to set the context item via the native protocol: (1) Insert a "declare context item" header into the document - Disadvantage: Should only work when XQUERY3 is true - Disadvantage: Modifies line/column refere

Re: [basex-talk] Delete attributes

Attributes are nodes, too [1]. Perhaps, you meant "and just the attribute, not the _element_". If so, the following query should do the job: delete nodes //@title Don't forget, that if you really want to shrink the database files, you need to execute OPTIMIZE ALL [2]. [1] http://www.w3.org/TR/

[basex-talk] Delete attributes

How do I delete attributes? (and just the attribute, not the node) Motivation: I have a db where 20% of the attributes is the same, 'title', which is never used. Deleting it could decrease the size of the db. /William Please consider the environment before prin

Re: [basex-talk] Any way to persist OutputStream in DiskData?

Christian, I had played around with the AUTOFLUSH option and did notice some improvement, which is great for my own uses when appropriate. If that option is set to false, how often does the database actually get flushed? Only on close? Does it flush before index rebuilds from Optimize? With th