Also, yes, it's just not supported. I wouldn't count on getting it supported anytime real soon. We might have a chance at DIY support once the widget architecture ships, if it still intends to be able to wrap other 3rd party libs like externals try to do for us now.
Andrew On Tue, Feb 10, 2015 at 10:35 AM, Dr. Hawkins <doch...@gmail.com> wrote: > It appears that, for reasons I cannot begin to imagine, SSL is only > supported for mySQL database connections, and not postgres. > > Is this correct? Does anyone know if there are plans to implement SSL for > postgres? > > At the moment, it seems that my only options are to either accept the > limitations of mySQL or to run a server on the postgres server that will > keep a socket open an dlisten to it. > > The "usual" solution that I find of server-side scripts that open a > database, run the query, and close it appear to be hard-core > nonstarters--it seems to take a significant fraction of a second to open a > database, even locally, and the queries every couple/few seconds need to > remain transparent to the user. > > Writing to the socket with a return message has strong appeal, and is > likely my best bet in any event, as it will allow the program to function > on a laggy connection. > > Nonetheless, ssl for postgres seems not to be a feature request, but > dealing with a massive security bug. > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Andrew Kluthe and...@ctech.me _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
