There was supposedly an effort to enable secure Postgres connection a few years ago, but it seems to have withered and died.
I had to give up on mysql for postgesql one the need to send compound queries. AFAIK, you still can’t do a block mysql transaction in mysql with livecode, making rollback impossible. (Well, I suppose you *could* do a big runaround with timestamps and faux “transaction” keys, but you’re still counting on the client end not failing). If I got forward with the project, I’m going to be encrypting the data at the client end. It limits the types of transactions possible, but that’s fine for what I do. (But an actual secure Postgres connection would be far better . . . ) _______________________________________________ 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
