Perhaps this helps - If I do the following
1. Open pil + from terminal 1 and run (pool "test.db")
2. Open pil + from terminal 2 and run (pool "test.db")
3. Run (put '{1} 'X 10) followed by (commit) in terminal 1
4. Run (get '{1} 'X) from terminal 2 -> we get 10 as expected
5. Run (put '{1} 'Y 20) followed by (commit) in terminal 1
6. Run (get '{1} 'Y) from terminal 2 -> this returns NIL
I suppose the two processes in the above sequence are not a family so the
scenario is not identical and perhaps the above is expected. I thought of
sharing just in case.
Regards,
Kashyap
On Wed, Aug 28, 2019 at 4:16 PM C K Kashyap <ckkash...@gmail.com> wrote:
> Hi Alex,
> I double checked and reloading the browser does not seem to help :(
> Regards,
> Kashyap
>
> On Wed, Aug 28, 2019 at 10:02 AM Alexander Burger <a...@software-lab.de>
> wrote:
>
>> Hi Kashyap,
>>
>> > I was trying out the guestbook example here -
>> > https://dev.to/cess11/lets-build-a-picolisp-guestbook-mkl I noticed
>> that
>> > the changes to the DB only get affected across sessions only after
>> restart
>> > the service. I mean, I add some data in a browser session and it shows
>> up
>> > at the bottom as expected, however, they disappear if I revisit the site
>> > from another tab.
>>
>> I have not tried or deeply studied the code, but it looks good at a first
>> glance.
>>
>> 'commit' should not be the culprit, as the program uses 'new!' and
>> 'put!>',
>> which commit automatically.
>>
>> Perhaps this is only a browser refresh problem? Browser tabs are not
>> automatically updated (contrary to pil's gui tabs) when revisited.
>>
>> What if you simply press the reload button in the browser's navigation
>> bar?
>>
>> ☺/ A!ex
>>
>> --
>> UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
>>
>
