Good smells for software packages #inductiveautomation #ignition

There is a concept of ‘code smells’

any characteristic in the source code of a program that possibly indicates a deeper problem.

I think there are some good smells for packaged software. Like fresh chocolate chip cookies.

The first and greatest is a great big button that says download to try it out, bonus points if I don’t have to register.


Letting you run the full suite for two hours at a time is also nice.

The nice fresh smell is to know how much the software costs without requesting a quote.

ignition pricing.PNG

Bonus points, an active forum



failed to initialize container mounts: failed to create overlay fs for container: mounting overlay solution GreenGrass

Greengrass currently doesn’t support Raspbian Buster or the latest kernel update for Raspbian Stretch, kernel 4.19.57. The Greengrass team is investigating what it will take to support kernel 4.19.57.

Before running apt-get upgrade be sure to block the latest kernel:

sudo apt-mark hold raspberrypi-bootloader
sudo apt-mark hold raspberrypi-kernel



Oracle Query Hint

Normally Oracle query hints will be written using /*+ ... */syntax. One day I spent many hours trying to figure out why one of my queries took forever to finish if I ran it from QlikView and took only a minute if I ran it from Oracle SQL Developer. Turned out that QlikView by default would strip out comments from SQL statement and treat /*+ ... */ as a comment.

This “feature” is discussed here.

Solution is easy – just use –+ syntax instead if you need to pass a query hint. Of course it is a very easy thing to forget!


Handy tool, Excel-SQLizer/

combine NT security with user name and password #qlikview section access

The trick is in the *

You can add reducing fields after the NTNAME


Section Access;



      ADMIN, ADMIN, welcome, *



Section Application;




Call stored procedure Oracle ODBC



Oracle in OraClient 12Home2, #Qlikview, and case of field names capitalization

This was an annoying one for a bit.

Say you have this Qlikview script




Select ORDER_NUMBER as Sales_Order from…. ;

Well, it won’t work because the Oracle ODBC driver uppers all the returned field names, or Oracle does? Who knows?

Anyways, to make it work