The sensors are offsite, but those locations don't filter outbound 3306, so no issues there. Sha1 is being used, and hosting companies allow inbound 3306 from known or any ip, based on a table. Tried the connector against 3 different versions of MySQL, and was not version dependent, so pretty sure if the protocol does not change, a PostGRES version would not need to be version dependent either. It's now working flawlessly in a production environment, logging weather sensor data from a number of mobile locations.
On Mon, Apr 28, 2014 at 8:25 AM, vincent elschot <vinny@xxxxxxxxx> wrote:
On 18-04-14 06:21, John R Pierce wrote:
On 4/17/2014 9:09 PM, Steve Spence wrote:
You know what? Fine, it doesn't matter that much to me. I'm happy to
continue using MySQL. It works with the Arduino quite nicely. Postgres
doesn't work. That's Postgres loss not mine. I really thought the
postgres team would be interested in providing support for a very
popular microcontroller system. If not, they are missing out on a
larger segment of users.
personal opinion:
I don't think a terminal device like a PC or an embedded system should be talking directly to SQL at all. instead, they should be talking to an application server which implements the "business logic", and THAT talks to the database
+1, especially if the sensors are located off-site, where sysadmins
have a tendency to close ports and filter protocols. HTTP gets through
pretty much any firewall without changes to the payload.
Also; using a native protocol means that the Arduino's must use the same version
as the server, which means you need a way to upgrade them, all at the same time.
Yikes.
Nope, I would dearly love to have a native PostgreSQL driver just to prove it can be done,
but I don't think it is a particularly good idea to actually use in production environments.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
