SE: restore default handlers?

classic Classic list List threaded Threaded
15 messages Options
Reply | Threaded
Open this post in threaded view
|

SE: restore default handlers?

Matthias Rebbe via use-livecode
I have "Show Default Handlers" checked in my SE, but I don't see them.

Is this yet another case where I have to toss my prefs stack and then go
back and restore all my settings to get this one thing to work, or is
there a simpler way to show default handlers in the SE?

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
Do you see the non-default handlers of the script?

If you see no handlers at all, then either there is a syntax error in the
script and LC for some reason does not see it, or something else happens
and trashing your Prefs will probably fix it :)

PS: I guess you have already tried unchecking and rechecking "Show default
handlers, correct?

Best,
Panos
--

On Tue, Feb 6, 2018 at 5:21 PM, Richard Gaskin via use-livecode <
[hidden email]> wrote:

> I have "Show Default Handlers" checked in my SE, but I don't see them.
>
> Is this yet another case where I have to toss my prefs stack and then go
> back and restore all my settings to get this one thing to work, or is there
> a simpler way to show default handlers in the SE?
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  [hidden email]                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
panagiotis merakos wrote:

 > On Tue, Feb 6, 2018 at 5:21 PM, Richard Gaskin wrote:
 >
 >> I have "Show Default Handlers" checked in my SE, but I don't see
 >> them.
...
 > Do you see the non-default handlers of the script?

Yes.

 > If you see no handlers at all, then either there is a syntax error in
 > the script and LC for some reason does not see it, or something else
 > happens and trashing your Prefs will probably fix it :)

The other day my car wouldn't start.  So I booted my laptop, tossed the
LiveCode preferences file, and everything was working again.  The right
answer for every problem. :)


 > PS: I guess you have already tried unchecking and rechecking "Show
 > default handlers, correct?

And again just now.

Filed:
http://quality.livecode.com/show_bug.cgi?id=20958

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.

Could it be the case that there is a bad interaction with a Plugin?

What happens if you try first to "put true into grevdevelopment" and then
uncheck and recheck "Show Default handlers"?

If something was failing silently before, this should now throw an error.

Best,
Panos
--

On Tue, Feb 6, 2018 at 6:03 PM, Richard Gaskin via use-livecode <
[hidden email]> wrote:

> panagiotis merakos wrote:
>
> > On Tue, Feb 6, 2018 at 5:21 PM, Richard Gaskin wrote:
> >
> >> I have "Show Default Handlers" checked in my SE, but I don't see
> >> them.
> ...
> > Do you see the non-default handlers of the script?
>
> Yes.
>
> > If you see no handlers at all, then either there is a syntax error in
> > the script and LC for some reason does not see it, or something else
> > happens and trashing your Prefs will probably fix it :)
>
> The other day my car wouldn't start.  So I booted my laptop, tossed the
> LiveCode preferences file, and everything was working again.  The right
> answer for every problem. :)
>
>
> > PS: I guess you have already tried unchecking and rechecking "Show
> > default handlers, correct?
>
> And again just now.
>
> Filed:
> http://quality.livecode.com/show_bug.cgi?id=20958
>
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  [hidden email]                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
panagiotis merakos wrote:
 > I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.
 >
 > Could it be the case that there is a bad interaction with a Plugin?
 >
 > What happens if you try first to "put true into grevdevelopment" and
 > then uncheck and recheck "Show Default handlers"?
 >
 > If something was failing silently before, this should now throw an
 > error.

Thanks.  Indeed it does - this is what I get pouring into the Message Box:


ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"
ERROR: unable to open database
unable to create sqlite API database
revdberr,invalid database type
line: 1079
handler: ideThrow
script object: stack
"/home/rg/.runrev/components/livecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibrary.8.livecodescript"

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
Thanks Richard. So, a guess is that for some reason LC cannot open the
sqlite database that holds all the dictionary entries, thus it cannot fetch
the list of the default handlers per object. I am wondering if this is
related to the other bug report you have filed, where the dictionary opens
but it is empty for you.

Let's delete the Documentation Cache:

1. Quit LC 9.0.0 DP-11
2. Delete folder: .runrev/documentationcache/9_0_0_dp_11_commercial/
3. Open LC
4. Check if the default handlers appear now.

Best,
Panos
--



On Tue, Feb 6, 2018 at 7:03 PM, Richard Gaskin via use-livecode <
[hidden email]> wrote:

> panagiotis merakos wrote:
> > I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.
> >
> > Could it be the case that there is a bad interaction with a Plugin?
> >
> > What happens if you try first to "put true into grevdevelopment" and
> > then uncheck and recheck "Show Default handlers"?
> >
> > If something was failing silently before, this should now throw an
> > error.
>
> Thanks.  Indeed it does - this is what I get pouring into the Message Box:
>
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
> ERROR: unable to open database
> unable to create sqlite API database
> revdberr,invalid database type
> line: 1079
> handler: ideThrow
> script object: stack "/home/rg/.runrev/components/l
> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> ry.8.livecodescript"
>
>
> --
>  Richard Gaskin
>  Fourth World Systems
>  Software Design and Development for the Desktop, Mobile, and the Web
>  ____________________________________________________________________
>  [hidden email]                http://www.FourthWorld.com
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
panagiotis merakos wrote:

> Thanks Richard. So, a guess is that for some reason LC cannot open the
> sqlite database that holds all the dictionary entries, thus it cannot fetch
> the list of the default handlers per object. I am wondering if this is
> related to the other bug report you have filed, where the dictionary opens
> but it is empty for you.
>
> Let's delete the Documentation Cache:
>
> 1. Quit LC 9.0.0 DP-11
> 2. Delete folder: .runrev/documentationcache/9_0_0_dp_11_commercial/
> 3. Open LC
> 4. Check if the default handlers appear now.

Good idea, but no go, still get:


 > ERROR: unable to open database
 > unable to create sqlite API database
 > revdberr,invalid database type
 > line: 1079
 > handler: ideThrow
 > script object: stack "/home/rg/.runrev/components/l
 > ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
 > ry.8.livecodescript"


It would be really cool if someone on the team could spend some time
doing daily work on Linux and Windows.  VMs are nice, but daily work on
metal will expose things beyond what customers report.  Not every day,
but a day a week would be an eye-opener.

For example, there's a weird scrolling issue I sometimes see on Linux,
in which the field my mouse is over is unaffected by my track pad
gestures, but some other field scrolls instead.  Sure, I could pin down
a recipe, and when I'm caught up on my deliverables from not being able
to use the Standalone Builder I'll try to make some time for recipes
like that.  But with daily work on these non-Mac OSes y'all would see
them first-hand, and if you did I doubt such things would survive for long.

--
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for the Desktop, Mobile, and the Web
  ____________________________________________________________________
  [hidden email]                http://www.FourthWorld.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
In reply to this post by Matthias Rebbe via use-livecode
Does this do what I think it does!? i.e. make it so rev code can throw errors, be debugged, breakpointed, and stepped through.

If so, oh my goodness you just made my day. I have been debugging  Navigator for fourteen years now, all with answer statements and puts. My code is literally riddled with commented-out ‘put “got here”’s

I can’t wait to get home to try this out...

gc

> On Feb 6, 2018, at 10:34 AM, panagiotis merakos via use-livecode <[hidden email]> wrote:
>
> What happens if you try first to "put true into grevdevelopment" and then
> uncheck and recheck "Show Default handlers"?

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
On 02/06/2018 02:46 PM, Geoff Canyon via use-livecode wrote:
> Does this do what I think it does!? i.e. make it so rev code can throw errors, be debugged, breakpointed, and stepped through.

Yes, it does... but be careful with it. It will also pinpoint all the
ugly errors in the IDE stacks. I only enable it when I'm trying to debug
my own system stacks, then turn if off again as soon as I've got things
working.

Also note that gRevDevelopment is a global, so
global gRevDevelopment; put true into gRevDevelopment
is what you need.

.. I set up a devolution button to enable/disable this feature, and it's
my most-used devolution option.

--
  Mark Wieder
  [hidden email]

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
On Tue, Feb 6, 2018 at 2:59 PM, Mark Wieder via use-livecode <
[hidden email]> wrote:

> On 02/06/2018 02:46 PM, Geoff Canyon via use-livecode wrote:
>
>> Does this do what I think it does!? i.e. make it so rev code can throw
>> errors, be debugged, breakpointed, and stepped through.
>>
>
> Yes, it does... but be careful with it. It will also pinpoint all the ugly
> errors in the IDE stacks. I only enable it when I'm trying to debug my own
> system stacks, then turn if off again as soon as I've got things working.
>
> ​Sure, but 90% of the work I do in LC is Navigator, so this is definitely
going into the Nav settings (at least my version of them).

gc​
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
In reply to this post by Matthias Rebbe via use-livecode
Of course, sqlite DBs are single user only so any attempt to open it a second time would fail. Just tossing that out there.

Bob S


> On Feb 6, 2018, at 11:30 , panagiotis merakos via use-livecode <[hidden email]> wrote:
>
> Thanks Richard. So, a guess is that for some reason LC cannot open the
> sqlite database that holds all the dictionary entries, thus it cannot fetch
> the list of the default handlers per object. I am wondering if this is
> related to the other bug report you have filed, where the dictionary opens
> but it is empty for you.
>
> Let's delete the Documentation Cache:
>
> 1. Quit LC 9.0.0 DP-11
> 2. Delete folder: .runrev/documentationcache/9_0_0_dp_11_commercial/
> 3. Open LC
> 4. Check if the default handlers appear now.
>
> Best,
> Panos
> --
>
>
>
> On Tue, Feb 6, 2018 at 7:03 PM, Richard Gaskin via use-livecode <
> [hidden email]> wrote:
>
>> panagiotis merakos wrote:
>>> I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.
>>>
>>> Could it be the case that there is a bad interaction with a Plugin?
>>>
>>> What happens if you try first to "put true into grevdevelopment" and
>>> then uncheck and recheck "Show Default handlers"?
>>>
>>> If something was failing silently before, this should now throw an
>>> error.
>>
>> Thanks.  Indeed it does - this is what I get pouring into the Message Box:
>>
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>> ERROR: unable to open database
>> unable to create sqlite API database
>> revdberr,invalid database type
>> line: 1079
>> handler: ideThrow
>> script object: stack "/home/rg/.runrev/components/l
>> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
>> ry.8.livecodescript"
>>
>>
>> --
>> Richard Gaskin
>> Fourth World Systems
>> Software Design and Development for the Desktop, Mobile, and the Web
>> ____________________________________________________________________
>> [hidden email]                http://www.FourthWorld.com
>>
>> _______________________________________________
>> use-livecode mailing list
>> [hidden email]
>> Please visit this url to subscribe, unsubscribe and manage your
>> subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
@Bob are you sure that's true?  I seem to recall being able to accidentally
reopen the db over and over without an error.  I can't remember if the dbid
increments when I do this, but I think it does.

On Wed, Feb 7, 2018 at 11:04 AM, Bob Sneidar via use-livecode <
[hidden email]> wrote:

> Of course, sqlite DBs are single user only so any attempt to open it a
> second time would fail. Just tossing that out there.
>
> Bob S
>
>
> > On Feb 6, 2018, at 11:30 , panagiotis merakos via use-livecode <
> [hidden email]> wrote:
> >
> > Thanks Richard. So, a guess is that for some reason LC cannot open the
> > sqlite database that holds all the dictionary entries, thus it cannot
> fetch
> > the list of the default handlers per object. I am wondering if this is
> > related to the other bug report you have filed, where the dictionary
> opens
> > but it is empty for you.
> >
> > Let's delete the Documentation Cache:
> >
> > 1. Quit LC 9.0.0 DP-11
> > 2. Delete folder: .runrev/documentationcache/9_0_0_dp_11_commercial/
> > 3. Open LC
> > 4. Check if the default handlers appear now.
> >
> > Best,
> > Panos
> > --
> >
> >
> >
> > On Tue, Feb 6, 2018 at 7:03 PM, Richard Gaskin via use-livecode <
> > [hidden email]> wrote:
> >
> >> panagiotis merakos wrote:
> >>> I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.
> >>>
> >>> Could it be the case that there is a bad interaction with a Plugin?
> >>>
> >>> What happens if you try first to "put true into grevdevelopment" and
> >>> then uncheck and recheck "Show Default handlers"?
> >>>
> >>> If something was failing silently before, this should now throw an
> >>> error.
> >>
> >> Thanks.  Indeed it does - this is what I get pouring into the Message
> Box:
> >>
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database
> >> revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >>
> >> --
> >> Richard Gaskin
> >> Fourth World Systems
> >> Software Design and Development for the Desktop, Mobile, and the Web
> >> ____________________________________________________________________
> >> [hidden email]                http://www.FourthWorld.com
> >>
> >> _______________________________________________
> >> use-livecode mailing list
> >> [hidden email]
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



--
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
Spiceworks Inventory and Help Desk uses a local sqlite dbfile. They stress that you cannot open this DB directly, or else if Spiceworks tries to write to it you can corrupt the DB. You *can* open the sqlite file read only, but two people cannot open it for write at the same time. sqlite is a single user database.

Bob S


> On Feb 7, 2018, at 10:44 , Mike Kerner via use-livecode <[hidden email]> wrote:
>
> @Bob are you sure that's true?  I seem to recall being able to accidentally
> reopen the db over and over without an error.  I can't remember if the dbid
> increments when I do this, but I think it does.


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: SE: restore default handlers?

Matthias Rebbe via use-livecode
In reply to this post by Matthias Rebbe via use-livecode
Mike,

Yes, the DBID will increment and the DB will be opened multiple time. I have
SQLite DBs open in the IDE while testing and open in MS Access via ODBC at
the same time. If both apps are reading then no problem. There is no real
good transactional record locking in SQLite. LC will throw an error if you
are  even reading the record in another program at the same time as an
update happens in LC. You can use these LC errors to do a retry for the
update.

Ralph DiMola
IT Director
Evergreen Information Services
[hidden email]

-----Original Message-----
From: use-livecode [mailto:[hidden email]] On Behalf
Of Mike Kerner via use-livecode
Sent: Wednesday, February 07, 2018 1:44 PM
To: How to use LiveCode
Cc: Mike Kerner
Subject: Re: SE: restore default handlers?

@Bob are you sure that's true?  I seem to recall being able to accidentally
reopen the db over and over without an error.  I can't remember if the dbid
increments when I do this, but I think it does.

On Wed, Feb 7, 2018 at 11:04 AM, Bob Sneidar via use-livecode <
[hidden email]> wrote:

> Of course, sqlite DBs are single user only so any attempt to open it a
> second time would fail. Just tossing that out there.
>
> Bob S
>
>
> > On Feb 6, 2018, at 11:30 , panagiotis merakos via use-livecode <
> [hidden email]> wrote:
> >
> > Thanks Richard. So, a guess is that for some reason LC cannot open
> > the sqlite database that holds all the dictionary entries, thus it
> > cannot
> fetch
> > the list of the default handlers per object. I am wondering if this
> > is related to the other bug report you have filed, where the
> > dictionary
> opens
> > but it is empty for you.
> >
> > Let's delete the Documentation Cache:
> >
> > 1. Quit LC 9.0.0 DP-11
> > 2. Delete folder: .runrev/documentationcache/9_0_0_dp_11_commercial/
> > 3. Open LC
> > 4. Check if the default handlers appear now.
> >
> > Best,
> > Panos
> > --
> >
> >
> >
> > On Tue, Feb 6, 2018 at 7:03 PM, Richard Gaskin via use-livecode <
> > [hidden email]> wrote:
> >
> >> panagiotis merakos wrote:
> >>> I cannot reproduce this, tested on Ubuntu 16.04 with LC 9 DP-11.
> >>>
> >>> Could it be the case that there is a bad interaction with a Plugin?
> >>>
> >>> What happens if you try first to "put true into grevdevelopment"
> >>> and then uncheck and recheck "Show Default handlers"?
> >>>
> >>> If something was failing silently before, this should now throw an
> >>> error.
> >>
> >> Thanks.  Indeed it does - this is what I get pouring into the
> >> Message
> Box:
> >>
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >> ERROR: unable to open database
> >> unable to create sqlite API database revdberr,invalid database type
> >> line: 1079
> >> handler: ideThrow
> >> script object: stack "/home/rg/.runrev/components/l
> >> ivecodeindy-9.0.0-dp-11.x86_64/Toolset/libraries/revidelibra
> >> ry.8.livecodescript"
> >>
> >>
> >> --
> >> Richard Gaskin
> >> Fourth World Systems
> >> Software Design and Development for the Desktop, Mobile, and the
> >> Web
____________________________________________________________________

> >> [hidden email]                http://www.FourthWorld.com
> >>
> >> _______________________________________________
> >> use-livecode mailing list
> >> [hidden email]
> >> Please visit this url to subscribe, unsubscribe and manage your
> >> subscription preferences:
> >> http://lists.runrev.com/mailman/listinfo/use-livecode
> >>
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



--
On the first day, God created the heavens and the Earth On the second day,
God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: SE: restore default handlers?

Matthias Rebbe via use-livecode
OIC I thought the question was, could 2 processes have the same sqlite db open. I don't think the LC engine opens the file over and over in different threads. I also think that it closes the connection when it is idle, hence the new DBID.

I just checked for sqlite V3, and it appears multiple processes *can* have the db opened but only one can write at the same time. I do not think that was true for older versions. I think too that Spiceworks tickles the db to keep the connection open continually. The following is from the sqlite FAQ:

Bob S

(5) Can multiple applications or multiple instances of the same application access a single database file at the same time?

Multiple processes can have the same database open at the same time. Multiple processes can be doing a SELECT at the same time. But only one process can be making changes to the database at any moment in time, however.

SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time. On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems.

We are aware of no other embedded SQL database engine that supports as much concurrency as SQLite. SQLite allows multiple processes to have the database file open at once, and for multiple processes to read the database at once. When any process wants to write, it must lock the entire database file for the duration of its update. But that normally only takes a few milliseconds. Other processes just wait on the writer to finish then continue about their business. Other embedded SQL database engines typically only allow a single process to connect to the database at once.

However, client/server database engines (such as PostgreSQL, MySQL, or Oracle) usually support a higher level of concurrency and allow multiple processes to be writing to the same database at the same time. This is possible in a client/server database because there is always a single well-controlled server process available to coordinate access. If your application has a need for a lot of concurrency, then you should consider using a client/server database. But experience suggests that most applications need much less concurrency than their designers imagine.

When SQLite tries to access a file that is locked by another process, the default behavior is to return SQLITE_BUSY. You can adjust this behavior from C code using the sqlite3_busy_handler() or sqlite3_busy_timeout() API functions.


> On Feb 7, 2018, at 10:56 , Ralph DiMola via use-livecode <[hidden email]> wrote:
>
> Mike,
>
> Yes, the DBID will increment and the DB will be opened multiple time. I have
> SQLite DBs open in the IDE while testing and open in MS Access via ODBC at
> the same time. If both apps are reading then no problem. There is no real
> good transactional record locking in SQLite. LC will throw an error if you
> are  even reading the record in another program at the same time as an
> update happens in LC. You can use these LC errors to do a retry for the
> update.
>
> Ralph DiMola


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode