bknr-devel

bknr-devel@common-lisp.net

57 discussions

[bknr-devel] bknr.datastore store lockfile
by Vladimir Sedach 02 Aug '12

02 Aug '12

Are there any plans to add a lockfile to bknr.datastore stores? Right now it seems possible for multiple Lisp processes to open the same store, and I'm not sure the resulting behavior is desirable. Another problem I noticed (at least with SBCL on Linux) is that taking a store whose directory permissions are owned by some user and opening it as a process running as root (for example, if running a daemon that opens the store before doing setuid) causes that store to be erased for some reason. Vladimir

2 3

[bknr-devel] BKNR.datastore snapshot frequency and old snapshots
by Vladimir Sedach 30 Dec '11

30 Dec '11

Hello, How often should a BKNR datastore be snapshot? I tried daily, but that is clearly too much. Is there a criteria (# of transaction since last snapshot) that can be used to determine this programmatically? Related to this, are snapshots linked to each other? Are old ones unneeded? Is it ok to delete them if they are? Vladimir

2 1

[bknr-devel] Deftransaction and &rest args
by Vladimir Sedach 13 Dec '11

13 Dec '11

Hello, Deftransaction permits &rest args, but they don't seem to be recorded in the store. Is the correct behavior that &rest args should not be valid in a deftransaction lambda-list, or is this a bug in storing them? Thanks, Vladimir

2 4

[bknr-devel] BKNR.datastore: support for serializing/deserializing arrays with complex (list) element-types
by Vladimir Sedach 10 Dec '11

10 Dec '11

Hi, I'd like to be able to store vectors of element-type '(unsigned-byte 8) using bknr.datastore. The included patch seems work to that end. Please consider it for inclusion. Thank you, Vladimir

2 4

[bknr-devel] Fork changes merged to git@github.com:hanshuebner/bknr-devel
by Hans Hübner 07 Dec '11

07 Dec '11

Hi, I have finally merged the changes from the two other forks (madnificient's and fsmunoz's) into master in my github repostory. Please let me know if there are any problems. -Hans

1 0

[bknr-devel] BKNR Porter stemmer
by Vladimir Sedach 07 Dec '11

07 Dec '11

The Porter stemmer from the BKNR repository is the one that comes with quicklisp. I noticed a bug when stemming the word "ion" due to the special case for that suffix. Attached is a patch. This bug isn't present in the code on Porter's own site (http://tartarus.org/martin/PorterStemmer/commonlisp.txt) Happy hacking, Vladimir

2 1

[bknr-devel] BKNR web, best place to start digging
by Frederico Muñoz 04 Jun '10

04 Jun '10

Hello, While working on the XML impex component I had a look around the web part of BKNR (which is the least documented). What would be the best project to use as a starting point? One would think that hello-web would be it, however I have been unable to to past hunchentoot internal errors, perhaps because the code doesn't reflect the current API. The same things happens with quickhoney, which is a bit stranger since I think that this one is more recent. Any advice welcome. As my previous message regarding XML impex I'm not looking for hand-holding or fixes (which is why I don't even post any concrete errors), merely a general pointer to where to start: this and that is a bit old, you would liekly be more lucky with that other one (or even forget about it, at this stage it would not be trivial to give any sort of indication). PS: My motivation is only that since I like the datastore component (with the indices, and now the XML impex) it would not be surprising if the rest is also something that I could use. However one can always use the datastore with other frameworks (e.g. weblocks, which seems to have some traction from what I've read, and uses cl-prevalence and Elephant as typical datastores - adding an example for the bknr datastore would be trivial).

2 8

Re: [bknr-devel] Problems with XML import/export, can't follow the tutorial
by Hans Hübner 01 Jun '10

01 Jun '10

With your changes on your local master and the github master reset to the old master, do a "git rebase -i origin/master". Squash all your commits into one, save and push to github. That should do. Let us know if it does not. -Hans Am 28.05.2010 20:49 schrieb "Frederico Muñoz" <fsmunoz(a)gmail.com>: Hi, 2010/5/28 Hans Hübner <hans.huebner(a)gmail.com>: > I'd prefer if you could eventually rebase your commits and squash them > into one before I pull th... I've tried to, but I'm afraid I probably didn't do it correctly. I reset my master by using upstream/master, forced the push to github, switch to my wip branch, did a git rebase master. The switched to my local master, merged the wip branch, and did a push. >From reading the docs I was expecting something more akin to a single commit, which isn't the case. I'm likely missing a step, or doing one to many. Regards, Frederico

2 7

Re: [bknr-devel] Problems with XML import/export, can't follow the tutorial
by Frederico Muñoz 28 May '10

28 May '10

Hello, 2010/5/27 Frederico Muñoz <fsmunoz(a)gmail.com>: (...) > I'll go back at it and hope to have something to show soon (well, for > relative values of soon). Well, I have pulled some changes to my github fork. The good news is that the tutorial now works. However, I'm sure that my changes could have been done is some better way - the code is not easy for me to follow. There are different approaches to how to do the exporting: I've maintained write-to-xml as the main one. It outputs to *standard-output*, or to any sink that is passed to it. I've made it a a macro (that is compatible with the usage seen in the tutorial) and renamed the original write-to-xml to build-xml (since it doesn't actuall write anything by itself). I haven't tested it deeply, but it mostly works. I'm now trying to understand the code better and see if there is any part in there that is a left-over of previous rewrites, etc. One of the things I will surely do is to document the functions - and also document the whole conversion process, since the way it works is sometimes hard to track. Regards, Frederico

2 5

Re: [bknr-devel] (no subject)
by Frederico Muñoz 28 May '10

28 May '10

Hello, > If you push, hans can do git diff on the two relevant revisions. Ok then, thanks for the hint, I guess it suffices then. PS: I've added the list to the Cc, your mail seemed to indicate that that was your intention but somewhere along the line it appears that some router didn't like the format of your message.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

bknr-devel