<hayley>
Hm, I got in trouble with that guy once. What sort of database storage do you want? (Suspecting you won't find much but it's useful to know what one would want.)
<prokhor_>
anything efficient & fast will do
jmdaemon has quit [Ping timeout: 255 seconds]
<prokhor_>
hayley: what was your fight with that guy about? (just for interest)...
Posterdati has quit [Read error: Connection reset by peer]
<hayley>
The fastest approach might be to keep data in memory, then write out a list of facts somehow. (But beware <https://www.youtube.com/watch?v=b2F-DItXtZs>, and perhaps the strong language in that, but a good warning in database design.)
<hayley>
prokhor_: Not a fight at all; just very mixed response to an article I co-authored.
<hayley>
The moral of the video, I figure, is that we still need to be careful about what semantics transactions have. Do you want all ACID?
bilegeek_ has quit [Quit: Leaving]
igemnace has joined #commonlisp
<prokhor_>
consistency for sure...
<prokhor_>
atomicity might enable me to partially do queries in parallel
<prokhor_>
or in short: I would not have to mess around with specific query strategies that much..
<prokhor_>
right?
<prokhor_>
wait!!! it would be better if it wouldnt force consistency though...
zachel has quit [Ping timeout: 244 seconds]
<hayley>
Consistency means that after you commit to the database, you will always observe the last written values, I think.
<hayley>
I'd be careful playing around with those things; the equivalent for shared memory would be using weaker memory models, which makes it harder to reason about the more ways a program could possibly run.
<prokhor_>
could you elaborate on that pls? (i am a noob in that field)... i've got my hands on a version of rcyc, so my ontology (probably) will be inconsistent... do you have experience with knowledgeworks? i am able to lay my hands too, if it only would help...
<hayley>
I don't. But what I imagine is that, suppose we have a program that just adds 1 to some number in the database. One transaction could read a 1, then write a 2. If the database is consistent, the next transaction has to read the 2, and then write 3. If not, the next transaction could read a 1, and not actually increment.
Dynom_ has joined #commonlisp
Dynom_ is now known as Guest3330
<hayley>
In the latter case, to understand what the program does, we have to consider what would happen if we don't read the value that was written last.
<prokhor_>
consistency with all previous transactions, i see...
contrapunctus has joined #commonlisp
azimut has quit [Ping timeout: 268 seconds]
azimut has joined #commonlisp
bitspook[m] has quit [Quit: You have been kicked for being idle]
<pve>
Hi! I was wondering if anyone "enriches" their default repl with utilities that should always be available (by loading them in the implementations init file)? Or do you prefer to just keep a bare cl-user and only load things depending on the task at hand?
<pve>
I find it a bit difficult to pick up this kind of knowledge by reading blogs or manuals.. the kind that probably is best learned by physically standing behind someone and observing them using the repl, emacs and all that
azimut_ has joined #commonlisp
azimut has quit [Ping timeout: 268 seconds]
* Nilby
runs a very very enriched repl
Inline has quit [Remote host closed the connection]
attila_lendvai has joined #commonlisp
Inline has joined #commonlisp
<pjb>
pve: you're a programmer, you can customize your REPL as you wish.
<pve>
pjb: heh, indeed
<edgar-rft>
let's use trivial-bitcoin to enrich our REPLs
<contrapunctus>
I've been meaning to modify my SLIME REPL prompt to show the current time, but I couldn't find any information about it.
varjag has quit [Ping timeout: 260 seconds]
asarch has joined #commonlisp
asarch has quit [Client Quit]
dra_ has joined #commonlisp
tibfulv has quit [Remote host closed the connection]
Inline has quit [Remote host closed the connection]
Inline has joined #commonlisp
Inline has quit [Remote host closed the connection]
jfb4 has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
<pjb>
contrapunctus: modifying slime will be an emacs lisp job.
<pjb>
contrapunctus: there's a slime-repl-insert-prompt function.
<pjb>
contrapunctus: it doesn't offer much hooks, it just calls: (slime-lisp-package-prompt-string), so the best is to just patch that function.
<pjb>
You could use a mode-line -like format instead of (format "%s> " (slime-lisp-package-prompt-string)) to configure it easily.
<pjb>
using (format-mode-line slime-prompt-format) with a new custom-variable named slime-prompt-format.
<pjb>
contrapunctus: then, you may try to post a PR to github, but they don't seem to be very receiptive to such "niche" patches, so perhaps we should consider switching to sly.
ebrasca has joined #commonlisp
azimut has quit [Remote host closed the connection]
azimut has joined #commonlisp
MajorBiscuit has joined #commonlisp
azimut has quit [Remote host closed the connection]
azimut has joined #commonlisp
gxt has quit [Remote host closed the connection]
gxt has joined #commonlisp
<jcowan>
datalog queries can be executed much more efficientlly by datalog engines than by prolog engines, and there is a good match between datalog and sql, whereas there is not between prolog and sql
azimut has quit [Ping timeout: 268 seconds]
gxt has quit [Ping timeout: 268 seconds]
mbrndtgn has quit [Quit: Bye!]
mbrndtgn has joined #commonlisp
azimut has joined #commonlisp
gxt has joined #commonlisp
azimut has quit [Remote host closed the connection]
azimut has joined #commonlisp
Inline has joined #commonlisp
causal has joined #commonlisp
<beach>
When is PROCLAIM preferable to DECLAIM?
<_death>
when you programmatically construct the declaration
<beach>
Good point. Thanks!
frgo has joined #commonlisp
<beach>
So it follows that PROCLAIM should not be used with a literal type specifier, right?
<_death>
do you mean declaration specifier?
<beach>
Oops, sorry. I was thinking of type proclamations only, but yes, you are right.
<_death>
if so, style-wise I'd say that's correct.. declaim is preferable.. there's also the note in the proclaim entry
<beach>
Oh, I'll check that out. Thanks.
<beach>
That note is pretty clear. Thanks again.
asarch has joined #commonlisp
mon_aaraj has quit [Ping timeout: 272 seconds]
mon_aaraj has joined #commonlisp
vassenn has joined #commonlisp
yauhsien has joined #commonlisp
zachel has joined #commonlisp
va55enn has joined #commonlisp
Lycurgus has joined #commonlisp
vassenn has quit [Ping timeout: 272 seconds]
okflo has quit [Quit: ZNC 1.6.3+deb1ubuntu0.2 - http://znc.in]
okflo has joined #commonlisp
pranavats has left #commonlisp [#commonlisp]
mon_aaraj has quit [Ping timeout: 244 seconds]
mon_aaraj has joined #commonlisp
taiju has quit [Ping timeout: 244 seconds]
yauhsien has quit [Remote host closed the connection]
yauhsien has joined #commonlisp
pranavats has joined #commonlisp
yauhsien has quit [Remote host closed the connection]
yauhsien has joined #commonlisp
pranavats has left #commonlisp [Error from remote client]
jmdaemon has joined #commonlisp
mon_aaraj has quit [Ping timeout: 255 seconds]
mon_aaraj has joined #commonlisp
dBc has quit [Quit: leaving]
yauhsien has quit [Remote host closed the connection]
EsoAlgo has quit [Ping timeout: 272 seconds]
gxt_ has joined #commonlisp
yauhsien has joined #commonlisp
gxt has quit [Remote host closed the connection]
ebrasca has quit [Ping timeout: 276 seconds]
Inline has quit [Remote host closed the connection]
Inline has joined #commonlisp
livoreno has joined #commonlisp
Inline has quit [Remote host closed the connection]
Inline has joined #commonlisp
Lycurgus has quit [Quit: Exeunt juan@acm.org]
chip2n has joined #commonlisp
yauhsien has quit [Remote host closed the connection]
yauhsien has joined #commonlisp
Oddity has joined #commonlisp
gxt_ has quit [Remote host closed the connection]
gxt_ has joined #commonlisp
yauhsien has quit [Remote host closed the connection]
tyson2 has quit [Remote host closed the connection]
aartaka has quit [Ping timeout: 255 seconds]
aartaka has joined #commonlisp
notzmv has quit [Ping timeout: 276 seconds]
igemnace has quit [Remote host closed the connection]
jmdaemon has quit [Ping timeout: 244 seconds]
jmdaemon has joined #commonlisp
ahlk has quit [Read error: Connection reset by peer]
asarch has quit [Quit: Leaving]
varjag has joined #commonlisp
va55enn has quit [Remote host closed the connection]
Volt_ has joined #commonlisp
aartaka has quit [Ping timeout: 272 seconds]
azimut has quit [Ping timeout: 268 seconds]
aartaka has joined #commonlisp
frgo has quit [Remote host closed the connection]
frgo has joined #commonlisp
frgo has quit [Read error: Connection reset by peer]
yauhsien has joined #commonlisp
yauhsien has quit [Remote host closed the connection]
ldb has joined #commonlisp
morganw has joined #commonlisp
Guest3330 has quit [Quit: WeeChat 3.5]
dra has quit [Quit: Leaving]
ldb has quit [Ping timeout: 268 seconds]
shka has quit [Ping timeout: 268 seconds]
ldb has joined #commonlisp
attila_lendvai has quit [Ping timeout: 272 seconds]
lucyy has joined #commonlisp
masinter has joined #commonlisp
Brucio-61 has quit [Remote host closed the connection]
Brucio-61 has joined #commonlisp
tyson2 has joined #commonlisp
lucyy has quit [Changing host]
lucyy has joined #commonlisp
ldb has quit [Quit: ERC 5.4 (IRC client for GNU Emacs 28.1)]
pve has quit [Quit: leaving]
santiagopim has joined #commonlisp
Guest8 has joined #commonlisp
frgo has joined #commonlisp
frgo has quit [Ping timeout: 264 seconds]
orestarod has quit [Ping timeout: 264 seconds]
morganw has quit [Remote host closed the connection]