UPDATE: The IndigoSqlClient has been replaced in Indigo 5.1.2 by the SQL Logger Plugin, which provides additional functionality and several improvements. This forum thread has been locked, so please post any questions about the SQL Logger Plugin in a new thread.

Note that the old IndigoSqlClient client will be removed by the installer, and the old database format (table names and rows defined in the tables) is [b]not compatible[b] with the new plugin. If you are using the old IndigoSqlClient then please read over the documentation on the new plugin so you can make adjustments to your scripts/SQL to be compatible with the new plugin.

PREVIOUS DETAILS ON DEPRECATED INDIGOSQLCLIENT:

The IndigoSqlClient can be used to efficiently save Indigo Device state changes, Variable value changes, and Event Log messages to either a SQLite database or a PostgreSQL database. IndigoSqlClient is a seperate process that Indigo Server can automatically launch (and terminate) that hooks into all device state and variable value change messages from the Indigo Server. This allows Indigo to integrate with other applications or systems, and allows for historical data tracking. You can, for example, use PHP to dynamically generate graphs or charts of device states (like temperature) stored in a PostgreSQL database.

You will have to install python version 2.5 or greater for SQLite support on OS X 10.4. I've never done that, so I don't have step-by-step instructions. You might just want to try PostgreSQL if you are running 10.4. I have gotten that working before.

The default python (/usr/bin/python) is probably still getting started. Try setting the $PATH variable in your .profile to point to the new python command. (you'll probably have to logout/back in for it to take effect)

So, apparently IndigoServer is running before the user's default shell is run (thus setting the new path). The only other thing I can think of is to link /usr/bin/python to the one at /Library/Frameworks/Python.framework/Versions/2.7/bin/ (be sure and keep the old /usr/bin/python in case linking doesn't work out). The only trick, of course, is if something else on your system requires the older version of python it might break. YMMV.

I tried the obvious, and disabled "Open at login" for Indigo, then restarted the computer. "python" and "sqlite3" in my /usr/bin/ directory both link to the new version of python I installed recently. Then I started Indigo server, but got the same error message about being unable to load the python sql module. I also tried using python 2.5 and got the same results.