[libreoffice-users] Re: Base to Heroku PostgreSQL requires "SSL=true"

Alexander Thurgood <alex.thurgood -AT- gmail.com>
Thu, 23 May 2013 12:38:54 +0200

Le 23/05/13 05:59, Richard Broermsa Jr. a écrit :

Hi Richard,

It might well be that a postgres SSL connection isn't supported in your
version of LO.

Which version of LO, which OS and which version of Java ? I don't know
whether the main developer of the LO postgres support code reads this
list very often, otherwise you will probably have to open up a bug report.


Alex



-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context

[libreoffice-users] Base to Heroku PostgreSQL requires "SSL=true" · Richard Broermsa Jr.
- Re: [libreoffice-users] Base to Heroku PostgreSQL requires "SSL=true" · Tom Davies
- [libreoffice-users] Re: Base to Heroku PostgreSQL requires "SSL=true" · Alexander Thurgood
  - [libreoffice-users] Re: Base to Heroku PostgreSQL requires "SSL=true" · Richard Broersma
    - Re: [libreoffice-users] Re: Base to Heroku PostgreSQL requires "SSL=true" · Tom Davies
- (message not available)
  - [libreoffice-users] subscription problems · Tom Davies

Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.