# Sqlite3 constant issues

**URL:** https://discourse.nodered.org/t/sqlite3-constant-issues/14090
**Category:** General
**Created:** [7 August 2019 11:25 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090 "2019-08-07T11:25:18Z")
**Posts on this page:** 9
**Page:** 2

<div class="post-metadata">

### Author: ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)
#### Post date: [9 August 2019 16:46 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/21 "2019-08-09T16:46:39Z")

</div>

Ran npm i --unsafe-perm node-red-node-sqlite@latest in the .node-red dir as user pi as suggested.

After lots of warnings.... it did the job. At that point, 2 other nodes needed updating so I did those then rebooted then checked palette manager, everything ok. I've no idea where the log file for that npm update would be, sorry. If anyone can point me to it I'll happily include any info. NR and all nodes are now up to date thanks.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [9 August 2019 17:19 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/22 "2019-08-09T17:19:33Z")

</div>

If it worked ok then don't need log I think. By log was meant the terminal output.  
I wonder whether you ran it from the wrong directory, or forgot the unsafe-perms the first time.

---

<div class="post-metadata">

### Author: ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)
#### Post date: [9 August 2019 17:58 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/23 "2019-08-09T17:58:11Z")

</div>

Possible Colin - well, now theres a record here for future ref... been my lucky evening so far, updated NR nodes, then apt-update - apt dist upgrade, apt upgrade and apt autoremove.. all perfect. (all sudo of course). Then checked NR again, all fine, doing a clone.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [10 August 2019 07:31 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/24 "2019-08-10T07:31:51Z")

</div>

Just to note for the future that `apt-get dist-upgrade` does everything that `apt-get upgrade` does and a bit more, so no need to do the second one.

---

<div class="post-metadata">

### Author: ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)
#### Post date: [10 August 2019 08:20 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/25 "2019-08-10T08:20:53Z")

</div>

Thank you Colin that is very helpful. Over time I'm getting there with help like this.

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [10 August 2019 18:23 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/26 "2019-08-10T18:23:41Z")

</div>

over time - apt has become more in favour (though apt-get hasn't been deprecated) - so `sudo apt update && sudo apt -yq dist-upgrade && sudo apt -yq autoremove && sudo apt -yq clean` does it for me.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [10 August 2019 20:07 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/27 "2019-08-10T20:07:41Z")

</div>

I think the 'official' command is `apt full-upgrade` rather than `dist-upgrade` though I see that `dist-upgrade` also works. I tend not to recommend `apt` for Raspbian yet as I don't think it works on Wheezy, but perhaps there are so few of those left around now though that I should not worry.

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [10 August 2019 22:34 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/28 "2019-08-10T22:34:30Z")

</div>

Good point. Yes it should be full-upgrade. And wheezy has been out of support for too long to be safe to use for anything connected.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [11 August 2019 07:53 UTC](https://discourse.nodered.org/t/sqlite3-constant-issues/14090/29 "2019-08-11T07:53:30Z")

</div>

Personally I wouldn't use the -yq on the upgrade either, I like to see what it is doing just in case something has gone wrong and it says it is, for example, going to uninstall a load of stuff it shouldn't. That is just a personal preference however, probably more to do with my geek level than anything else.

[Previous page](https://discourse.nodered.org/t/sqlite3-constant-issues/14090.md?page=1)
