record locks in Run Basic

[badbug]

I'm fairly new to LB and RB.
I'm testing a program in Run Basic using SQLite. 
Not sure why, but sometimes it locks up. It appears that Run Basic is somehow not releasing the lock.
The only way I can find to correct it to stop RunBasic and start it again.

I'll give it another try when this is fixed.
IF not, I'll have to try something like xojo, spiderBasic, or Real basic.
PHP is a nightmare trying to keep track of all the variables by passing them in hidden inputs.

Thanks for the help,
EB

[Rod]

If you could provide a short coding example that creates the problem you would have more of a chance of Carl looking at it. A very short easy to read example.

Even then Carl has not been seen to work on Run BASIC for quite some time.

The problem has been discussed in the past but the examples that creat the problem were long and complex. So giving a very concise example might peak his interest.

[metro]

I think Carl suspects he has found the issue already.
Sadly his life has been far too busy to dive in deeper.

Mar 26, 2020 23:31:09 GMT -5 Carl Gundel said:

Mar 26, 2020 13:22:34 GMT -5 Carl Gundel said:

Pretty sure that isn't fixed.  I did investigate but then got distracted by other things, sorry.  I'll refocus.

Okay, I think I have some good news about this.  It seems that LB5 wasn't cleaning the cursors up properly between execute commands.  It wasn't obvious from the Smalltalk SQLite library API that this is needed.  There is a disconnect function that needs to be called after a cursor is used.  Each new execute gets a new cursor, and the last one needs to be sent disconnect.

When I add this in the LB5 lock test monster example runs to completion without error.

And just maybe this is also the problem with RB.

But I haven't done a build in a very long time and it will take a concerted effort to rework the build process, and right now I'm working on Liberty BASIC and this is the wrong time to shift gears.

[badbug]

If you could provide a short coding example that creates the problem you would have more of a chance of Carl looking at it. A very short easy to read example.

After looking at the "lock test monster" that was used to solve the LB problem, it's only about 3 lines long with a very simple sql query.
It locked every time. After the fix in LB, no more SQLite lock ups.

So it's as simple as you can possibly get...
Since they both use the same logic, why not apply the fixes to the RB probelm?

LB just doesn't have a web presense, and I need the web. So I'm looking at alternatives.. To bad since RB is got the answers I want.
Frank