On Mon, 24 Feb 2014 11:00:45 +0100
Alex Thurgood <firstname.lastname@example.org> wrote:
Le 22/02/2014 19:11, Jim Seymour a écrit :
For starters: LibréOffice 18.104.22.168, Build ID: 350m1 (Build: 2)
Before anybody suggests a newer version: I'm currently on Ubuntu
10.04 LTS (Lucid Lynx), so I'm stuck with it. (Even my much newer
Linux Mint desktop install at work is still 3.x, I believe.)
You should be able to install newer versions even on Ubuntu 10.04 LTS,
if you download them from the LibreOffice website. Of course, they
won't necessarily have full desktop integration, although Unity came
after 10.04, so it should be OK.
I followed the instructions for adding the proper repository and
installed with apt-get. 22.214.171.124 is what it gave me.
As for Linux Mint, I have Mint 15 and 16 on two separate machines.
Both have (at least I think they do) more recent packaged versions of
LO in their repos than 3.5.7 (Mint 16 : LO 126.96.36.199).
I have Mint 13 at work. It isn't all *that* old. Only installed about
a year ago, if memory serves. Yes: I see 15 and 16 are now available.
Anyway: 188.8.131.52 at work, on my Mint 13 machine, as well.
I have 4.1.something under MS-Win on my work laptop. Haven't played
with that, yet. (Have yet to work out the self-signed CA cert with
keytool under MS-Win.)
Anyway, as that
is not necessarily an immediate solution to your problem, on to the
meat of the question :
I have a database with a couple tables, as in
create table hdwr_assets (
atag text primary key,
serno text unique,
status_id int references hdwr_status,
-- e.g.: "deployed", "in stock"
create table hdwr_status (
status_id serial primary key,
descr text not null,
The plan was to create a form that could query and alter hardware
assets, selecting values for status_id from a drop-down list, the
available selection being from the hardware status table.
Does the LEFT JOIN query with a single join actually run from the
Query Designer or do you get an error ?
The left join works in Query Designer. I get the same thing as I would
with an ad hoc query via psql.
Does it make any difference if you turn off/on the Direct SQL button
(which causes the query to bypass the internal LO SQL parser, or
alternatively, ask it to interpret the query before fielding it to the
JDBC driver) ?
I did not try those things. Didn't know about them. I'll look into it.
What are the settings in the "Advanced Options" of your db connection
for that ODB file ?
"Edit -> Advanced Settings -> Database -> Special Settings", perhaps?
Options checked are:
Ignore the privileges from the database driver
Use catalog name in SELECT statements
Use schema name in SELECT statements
Create index with ASC or DESC statement
Form data input checks for required fields
Use ODBC conformant data/time literals
Comparison of Boolean values: Default
Which driver version of JDBC are you using ?
Which version of postgres ?
PostgreSQL v8.4.19 w/postgresql-jdbc4-9.1.jar at work
PostgreSQL v8.4.19 w/postgresql-jdbc3-8.4.jar at home
Behaviour is the same at both locations.
Alex (yes, yet another)
Thanks for the follow-up, Alex the III :)
Note: My mail server employs *very* aggressive anti-spam
filtering. If you reply to this email and your email is
rejected, please accept my apologies and let me know via my
web form at <http://jimsun.LinxNet.com/contact/scform.php>.
To unsubscribe e-mail to: email@example.com
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
Impressum (Legal Info)
: 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