Thread: problem with update data sets from front ends 8.4, Ubuntu 10.04
postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new install)
I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other
updates have been effected. I used webmin to restore the databases.
Since migrating to Linux around 2006 we were successful in converting our mdb
file to postgresql - only one glitch was a difference in -1 as YES. We
successfully used the systems with open office as a front end for the last few
years. Until now - after the upgrade I can view data but not update data.
Experience with sql is very limited as I have always used sql query builders
over the years. The system has worked well with multiple tables, and in the
past there was no problems with sending sql statements to postgresql.
My problem in OOO 3.2 base (other front ends also) is that there is
continually a problem with not allowing queries to update data back to
postgresql.
I believe something has changed perhaps in sql from 8.3 to 8.4, or I have
missed something with restoring the files.
I enclose a typical sql statement for a table.
-- Table: "FINANCEDETAILS"
-- DROP TABLE "FINANCEDETAILS";
CREATE TABLE "FINANCEDETAILS"
( "FINDETID" serial NOT NULL, "INVREF" integer DEFAULT 0, "INITIALFINDATE" timestamp without time zone, "RESTARTFIN"
timestampwithout time zone, "PAYDAY" integer DEFAULT 1, "AMOUNT" double precision DEFAULT (0)::double precision,
"DEBITACC"integer DEFAULT 1, "DEBITDIVNO" integer, "CREDITACC" integer DEFAULT 0, "CREDDIVNO" integer,
"TRANSDESCRIPTION"character varying(50) DEFAULT 'Support'::character
varying, "COMMITMENT" character varying(50) DEFAULT 'Casual'::character varying, "SUPPORTBY" character varying(25),
"EXPDATE"timestamp without time zone, "BANK" character varying(50), "BRANCH" character varying(50), "BRANCHCODE"
charactervarying(50), "BKACCOUNTTYPE" character varying(50) DEFAULT 'Cheque'::character varying, "ACCOUNTNUMBER"
charactervarying(50), "TYPETRANS" integer DEFAULT 0, "REMITTANCE" boolean, "RECEIPT" boolean, "JOURNAL" boolean,
"VOUCHERREQ"boolean, "STANDINGORDER" boolean, "STDORDAUTHDETAILS" text, "OLDFINREF" numeric, "COMMENTS" text,
CONSTRAINT"FINANCEDETAILS_pkey" PRIMARY KEY ("FINDETID"), CONSTRAINT "FINANCEDETAILS_FINDETID_key" UNIQUE ("FINDETID")
)
WITH ( OIDS=TRUE
);
ALTER TABLE "FINANCEDETAILS" OWNER TO dean;
GRANT ALL ON TABLE "FINANCEDETAILS" TO public;
# -----------------------------
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form:
#
# name = value
#
# (The "=" is optional.) Whitespace may be used. Comments are introduced
with
# "#" anywhere on a line. The complete list of parameter names and allowed
# values can be found in the PostgreSQL documentation.
#
# The commented-out settings shown in this file represent the default values.
# Re-commenting a setting is NOT sufficient to revert it to the default value;
# you need to reload the server.
#
# This file is read on server startup and when the server receives a SIGHUP
# signal. If you edit the file on a running system, you have to SIGHUP the
# server for the changes to take effect, or use "pg_ctl reload". Some
# parameters, which are marked below, require a server shutdown and restart to
# take effect.
#
# Any parameter can also be given as a command-line option to the server,
e.g.,
# "postgres -c log_connections=on". Some parameters can be changed at run
time
# with the "SET" SQL command.
#
# Memory units: kB = kilobytes Time units: ms = milliseconds
# MB = megabytes s = seconds
# GB = gigabytes min = minutes
# h = hours
# d = days
#------------------------------------------------------------------------------
# FILE LOCATIONS
#------------------------------------------------------------------------------
# The default values of these variables are driven from the -D command-line
# option or PGDATA environment variable, represented here as ConfigDir.
data_directory = '/var/lib/postgresql/8.4/main' # use data in another
directory # (change requires restart)
hba_file = '/etc/postgresql/8.4/main/pg_hba.conf' # host-based authentication
file # (change requires restart)
ident_file = '/etc/postgresql/8.4/main/pg_ident.conf' # ident configuration
file # (change requires restart)
# If external_pid_file is not explicitly set, no extra PID file is written.
external_pid_file = '/var/run/postgresql/8.4-main.pid' # write an
extra PID file # (change requires restart)
#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------
# - Connection Settings -
#listen_addresses = 'localhost' # what IP address(es) to listen on; # comma-separated list of
addresses; # defaults to 'localhost', '*' = all # (change requires restart)
port = 5432 # (change requires restart)
max_connections = 100 # (change requires restart)
# Note: Increasing max_connections costs ~400 bytes of shared memory per
# connection slot, plus lock space (see max_locks_per_transaction).
#superuser_reserved_connections = 3 # (change requires restart)
unix_socket_directory = '/var/run/postgresql' # (change requires
restart)
#unix_socket_group = '' # (change requires restart)
#unix_socket_permissions = 0777 # begin with 0 to use octal notation # (change requires restart)
#bonjour_name = '' # defaults to the computer name # (change requires restart)
# - Security and Authentication -
#authentication_timeout = 1min # 1s-600s
ssl = true # (change requires restart)
#ssl_ciphers = 'ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH' # allowed SSL ciphers # (change requires restart)
#ssl_renegotiation_limit = 512MB # amount of data between renegotiations
#password_encryption = on
#db_user_namespace = off
# Kerberos and GSSAPI
#krb_server_keyfile = ''
#krb_srvname = 'postgres' # (Kerberos only)
#krb_caseins_users = off
# - TCP Keepalives -
# see "man 7 tcp" for details
#tcp_keepalives_idle = 0 # TCP_KEEPIDLE, in seconds; # 0 selects the system default
#tcp_keepalives_interval = 0 # TCP_KEEPINTVL, in seconds; # 0 selects the system default
#tcp_keepalives_count = 0 # TCP_KEEPCNT; # 0 selects the system default
#------------------------------------------------------------------------------
# RESOURCE USAGE (except WAL)
#------------------------------------------------------------------------------
# - Memory -
shared_buffers = 28MB # min 128kB # (change requires restart)
#temp_buffers = 8MB # min 800kB
#max_prepared_transactions = 0 # zero disables the feature # (change requires restart)
# Note: Increasing max_prepared_transactions costs ~600 bytes of shared
memory
# per transaction slot, plus lock space (see max_locks_per_transaction).
# It is not advisable to set max_prepared_transactions nonzero unless you
# actively intend to use prepared transactions.
#work_mem = 1MB # min 64kB
#maintenance_work_mem = 16MB # min 1MB
#max_stack_depth = 2MB # min 100kB
# - Kernel Resource Usage -
#max_files_per_process = 1000 # min 25 # (change requires restart)
#shared_preload_libraries = '' # (change requires restart)
# - Cost-Based Vacuum Delay -
#vacuum_cost_delay = 0ms # 0-100 milliseconds
#vacuum_cost_page_hit = 1 # 0-10000 credits
#vacuum_cost_page_miss = 10 # 0-10000 credits
#vacuum_cost_page_dirty = 20 # 0-10000 credits
#vacuum_cost_limit = 200 # 1-10000 credits
# - Background Writer -
#bgwriter_delay = 200ms # 10-10000ms between rounds
#bgwriter_lru_maxpages = 100 # 0-1000 max buffers written/round
#bgwriter_lru_multiplier = 2.0 # 0-10.0 multipler on buffers scanned/round
# - Asynchronous Behavior -
#effective_io_concurrency = 1 # 1-1000. 0 disables prefetching
#------------------------------------------------------------------------------
# WRITE AHEAD LOG
#------------------------------------------------------------------------------
# - Settings -
#fsync = on # turns forced synchronization on or off
#synchronous_commit = on # immediate fsync at commit
#wal_sync_method = fsync # the default is the first option # supported by the operating system:
# open_datasync # fdatasync (default on Linux) # fsync
# fsync_writethrough # open_sync
#full_page_writes = on # recover from partial page writes
#wal_buffers = 64kB # min 32kB # (change requires restart)
#wal_writer_delay = 200ms # 1-10000 milliseconds
#commit_delay = 0 # range 0-100000, in microseconds
#commit_siblings = 5 # range 1-1000
# - Checkpoints -
#checkpoint_segments = 3 # in logfile segments, min 1, 16MB each
#checkpoint_timeout = 5min # range 30s-1h
#checkpoint_completion_target = 0.5 # checkpoint target duration, 0.0 - 1.0
#checkpoint_warning = 30s # 0 disables
# - Archiving -
#archive_mode = off # allows archiving to be done # (change requires restart)
#archive_command = '' # command to use to archive a logfile segment
#archive_timeout = 0 # force a logfile segment switch after this # number of seconds; 0 disables
#------------------------------------------------------------------------------
# QUERY TUNING
#------------------------------------------------------------------------------
# - Planner Method Configuration -
enable_bitmapscan = on
enable_hashagg = on
enable_hashjoin = on
enable_indexscan = on
enable_mergejoin = on
#enable_nestloop = on
#enable_seqscan = on
#enable_sort = on
enable_tidscan = on
# - Planner Cost Constants -
#seq_page_cost = 1.0 # measured on an arbitrary scale
#random_page_cost = 4.0 # same scale as above
#cpu_tuple_cost = 0.01 # same scale as above
#cpu_index_tuple_cost = 0.005 # same scale as above
#cpu_operator_cost = 0.0025 # same scale as above
#effective_cache_size = 128MB
# - Genetic Query Optimizer -
geqo = on
geqo_threshold = 12
geqo_effort = 5 # range 1-10
geqo_pool_size = 0 # selects default based on effort
geqo_generations = 0 # selects default based on effort
geqo_selection_bias = 2.0 # range 1.5-2.0
# - Other Planner Options -
#default_statistics_target = 100 # range 1-10000
#constraint_exclusion = partition # on, off, or partition
#cursor_tuple_fraction = 0.1 # range 0.0-1.0
#from_collapse_limit = 8
#join_collapse_limit = 8 # 1 disables collapsing of explicit # JOIN clauses
#------------------------------------------------------------------------------
# ERROR REPORTING AND LOGGING
#------------------------------------------------------------------------------
# - Where to Log -
#log_destination = 'stderr' # Valid values are combinations of # stderr, csvlog, syslog and
eventlog, # depending on platform. csvlog # requires logging_collector to be on.
# This is used when logging to stderr:
#logging_collector = off # Enable capturing of stderr and csvlog # into log files. Required to be
onfor # csvlogs. # (change requires restart)
# These are only used if logging_collector is on:
#log_directory = 'pg_log' # directory where log files are written, # can be absolute or relative
toPGDATA
#log_filename = 'postgresql-%Y-%m-%d_%H%M%S.log' # log file name pattern, # can include strftime()
escapes
#log_truncate_on_rotation = off # If on, an existing log file of the # same name as the new log
filewill be # truncated rather than appended to. # But such truncation only occurs on
# time-driven rotation, not on restarts # or size-driven rotation. Default is
#off, meaning append to existing files # in all cases.
#log_rotation_age = 1d # Automatic rotation of logfiles will # happen after that time. 0
disables.
#log_rotation_size = 10MB # Automatic rotation of logfiles will # happen after that much log
output. # 0 disables.
# These are relevant when logging to syslog:
#syslog_facility = 'LOCAL0'
#syslog_ident = 'postgres'
#silent_mode = off # Run server silently. # DO NOT USE without syslog or #
logging_collector # (change requires restart)
# - When to Log -
#client_min_messages = notice # values in order of decreasing detail: # debug5 #
debug4 # debug3 # debug2 # debug1 # log
# notice # warning # error
#log_min_messages = warning # values in order of decreasing detail: # debug5 #
debug4 # debug3 # debug2 # debug1 # info
# notice # warning # error # log # fatal
# panic
#log_error_verbosity = default # terse, default, or verbose messages
#log_min_error_statement = error # values in order of decreasing detail: # debug5 #
debug4 # debug3 # debug2 # debug1 # info
# notice # warning # error # log # fatal
# panic (effectively off)
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements # and their durations, > 0
logsonly # statements running at least this number # of milliseconds
# - What to Log -
#debug_print_parse = off
#debug_print_rewritten = off
#debug_print_plan = off
#debug_pretty_print = on
#log_checkpoints = off
#log_connections = off
#log_disconnections = off
#log_duration = off
#log_hostname = off
log_line_prefix = '%t ' # special values: # %u = user name # %d = database
name # %r = remote host and port # %h = remote host # %p = process ID
# %t = timestamp without milliseconds # %m = timestamp with milliseconds
# %i = command tag # %c = session ID # %l = session line number #
%s= session start timestamp # %v = virtual transaction ID # %x = transaction ID (0 if
none) # %q = stop here in non-session # processes # %% = '%'
# e.g. '<%u%%%d> '
#log_lock_waits = off # log lock waits >= deadlock_timeout
#log_statement = 'none' # none, ddl, mod, all
#log_temp_files = -1 # log temporary files equal or larger # than the specified size in
kilobytes; # -1 disables, 0 logs all temp files
#log_timezone = unknown # actually, defaults to TZ environment # setting
#------------------------------------------------------------------------------
# RUNTIME STATISTICS
#------------------------------------------------------------------------------
# - Query/Index Statistics Collector -
#track_activities = on
#track_counts = on
#track_functions = none # none, pl, all
#track_activity_query_size = 1024
#update_process_title = on
#stats_temp_directory = 'pg_stat_tmp'
# - Statistics Monitoring -
#log_parser_stats = off
#log_planner_stats = off
#log_executor_stats = off
#log_statement_stats = off
#------------------------------------------------------------------------------
# AUTOVACUUM PARAMETERS
#------------------------------------------------------------------------------
#autovacuum = on # Enable autovacuum subprocess? 'on' # requires track_counts to also be
on.
#log_autovacuum_min_duration = -1 # -1 disables, 0 logs all actions and # their durations, > 0 logs
only # actions running at least this number # of milliseconds.
#autovacuum_max_workers = 3 # max number of autovacuum subprocesses
#autovacuum_naptime = 1min # time between autovacuum runs
#autovacuum_vacuum_threshold = 50 # min number of row updates before # vacuum
#autovacuum_analyze_threshold = 50 # min number of row updates before # analyze
#autovacuum_vacuum_scale_factor = 0.2 # fraction of table size before
vacuum
#autovacuum_analyze_scale_factor = 0.1 # fraction of table size before
analyze
#autovacuum_freeze_max_age = 200000000 # maximum XID age before forced vacuum # (change requires
restart)
#autovacuum_vacuum_cost_delay = 20ms # default vacuum cost delay for # autovacuum, in milliseconds;
# -1 means use vacuum_cost_delay
#autovacuum_vacuum_cost_limit = -1 # default vacuum cost limit for # autovacuum, -1 means use
# vacuum_cost_limit
#------------------------------------------------------------------------------
# CLIENT CONNECTION DEFAULTS
#------------------------------------------------------------------------------
# - Statement Behavior -
#search_path = '"$user",public' # schema names
#default_tablespace = '' # a tablespace name, '' uses the default
#temp_tablespaces = '' # a list of tablespace names, '' uses # only default tablespace
#check_function_bodies = on
#default_transaction_isolation = 'read committed'
#default_transaction_read_only = off
#session_replication_role = 'origin'
#statement_timeout = 0 # in milliseconds, 0 is disabled
#vacuum_freeze_min_age = 50000000
#vacuum_freeze_table_age = 150000000
#xmlbinary = 'base64'
#xmloption = 'content'
# - Locale and Formatting -
datestyle = 'iso, dmy'
#intervalstyle = 'postgres'
#timezone = unknown # actually, defaults to TZ environment # setting
#timezone_abbreviations = 'Default' # Select the set of available time
zone # abbreviations. Currently, there are # Default # Australia
# India # You can create your own file in # share/timezonesets/.
#extra_float_digits = 0 # min -15, max 2
#client_encoding = sql_ascii # actually, defaults to database # encoding
# These settings are initialized by initdb, but they can be changed.
lc_messages = 'en_ZA.utf8' # locale for system error message # strings
lc_monetary = 'en_ZA.utf8' # locale for monetary formatting
lc_numeric = 'en_ZA.utf8' # locale for number formatting
lc_time = 'en_ZA.utf8' # locale for time formatting
# default configuration for text search
default_text_search_config = 'pg_catalog.english'
# - Other Defaults -
#dynamic_library_path = '$libdir'
#local_preload_libraries = ''
#------------------------------------------------------------------------------
# LOCK MANAGEMENT
#------------------------------------------------------------------------------
#deadlock_timeout = 1s
#max_locks_per_transaction = 64 # min 10 # (change requires restart)
# Note: Each lock table slot uses ~270 bytes of shared memory, and there are
# max_locks_per_transaction * (max_connections + max_prepared_transactions)
# lock table slots.
#------------------------------------------------------------------------------
# VERSION/PLATFORM COMPATIBILITY
#------------------------------------------------------------------------------
# - Previous PostgreSQL Versions -
#add_missing_from = off
#array_nulls = on
#backslash_quote = safe_encoding # on, off, or safe_encoding
#default_with_oids = off
#escape_string_warning = on
#regex_flavor = advanced # advanced, extended, or basic
#sql_inheritance = on
#standard_conforming_strings = off
#synchronize_seqscans = on
# - Other Platforms and Clients -
#transform_null_equals = off
#------------------------------------------------------------------------------
# CUSTOMIZED OPTIONS
#------------------------------------------------------------------------------
#custom_variable_classes = '' # list of custom variable class names
# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the
# PostgreSQL documentation for a complete description
# of this file. A short synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access. Records take one of these forms:
#
# local DATABASE USER METHOD [OPTIONS]
# host DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain socket,
# "host" is either a plain or SSL-encrypted TCP/IP socket, "hostssl" is an
# SSL-encrypted TCP/IP socket, and "hostnossl" is a plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", a database name, or
# a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or
# a comma-separated list thereof. In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names from
# a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.
# It is made up of an IP address and a CIDR mask that is an integer
# (between 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies
# the number of significant bits in the mask. Alternatively, you can write
# an IP address and netmask in separate columns to specify the set of hosts.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi", "krb5",
# "ident", "pam", "ldap" or "cert". Note that "password" sends passwords
# in clear text; "md5" is preferred since it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE. The available options depend on the different authentication
# methods - refer to the "Client Authentication" section in the documentation
# for a list of which options are available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other special
# characters must be quoted. Quoting one of the keywords "all", "sameuser" or
# "samerole" makes the name lose its special character, and just match a
# database or username with that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal. If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect. You can use
# "pg_ctl reload" to do that.
# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records. In that case you will also need to make PostgreSQL listen
# on a non-local interface via the listen_addresses configuration parameter,
# or via the -i or -h command line switches.
#
# DO NOT DISABLE!
# If you change this first entry you will need to make sure that the
# database
# super user can access the database using some other method.
# Noninteractive
# access to all databases is required during automatic maintenance
# (custom daily cronjobs, replication, and similar tasks).
#
# Database administrative login by UNIX sockets
local all postgres ident
# TYPE DATABASE USER CIDR-ADDRESS METHOD
# "local" is for Unix domain socket connections only
local all postgres md5
local all all ident
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5
Any assistance offered will be appreciated.
On Mon, May 23, 2011 at 9:53 AM, Dean le Roux <projserve@gmail.com> wrote:
postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new install)
I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other
updates have been effected. I used webmin to restore the databases.
Since migrating to Linux around 2006 we were successful in converting our mdb
file to postgresql - only one glitch was a difference in -1 as YES. We
successfully used the systems with open office as a front end for the last few
years. Until now - after the upgrade I can view data but not update data.
Experience with sql is very limited as I have always used sql query builders
over the years. The system has worked well with multiple tables, and in the
past there was no problems with sending sql statements to postgresql.
My problem in OOO 3.2 base (other front ends also) is that there is
continually a problem with not allowing queries to update data back to
postgresql.
I believe something has changed perhaps in sql from 8.3 to 8.4, or I have
missed something with restoring the files.
At minimum, we need to see the update statement that you are attempting to execute, preferably with any error message you receive.
Here is the sql statements. We don't pass update, I guess base or the relevant
programmes does that. Some transactions that are based on forms seem to
update, but sometimes they don't, and it would seem that certain constraints
are not met, causing holes in the database. This didn't happen prior to
upgrade - it would tell you that you couldn't delete the record, upholding
constraints.
SELECT "HOMINVOLV"."PROJREF", "HOMNLPOST"."LANGREF", "HOMINVOLV"."HISTORYREC",
"HOMINVOLV"."RESTRICTEDACCESS", "HOMADDRESS"."ADDRESSSTOP",
"HOMNLPOST"."SENDNL", "HOMINVOLV"."TITLEREF", "HOMINVOLV"."INITIALS",
"HOMNLPOST"."PERSNAME", "HOMCONT"."LASTNAME", "HOMCONCERN"."POSTHELD",
"HOMCONCERN"."CONCERN", "HOMCONCERN"."BRANCHOFCONC", "HOMADDRESS"."ADD1",
"HOMADDRESS"."ADD2", "HOMADDRESS"."ADD3", "HOMADDRESS"."ADD4",
"HOMADDRESS"."ADD5", "HOMADDRESS"."ADD6", "HOMNLPOST"."ENVELOPE",
"HOMINVOLV"."INVREF", "HOMNLPOST"."AFRIGREET" FROM { OJ "public"."HOMCONCERN"
AS "HOMCONCERN" RIGHT OUTER JOIN "public"."HOMCONT" AS "HOMCONT" RIGHT OUTER
JOIN "public"."HOMINVOLV" AS "HOMINVOLV" RIGHT OUTER JOIN
"public"."HOMADDRESS" AS "HOMADDRESS" LEFT OUTER JOIN "public"."HOMNLPOST" AS
"HOMNLPOST" ON "HOMADDRESS"."ADDREF" = "HOMNLPOST"."ADDREF" ON
"HOMINVOLV"."INVREF" = "HOMNLPOST"."INVREF" ON "HOMCONT"."CONTREF" =
"HOMADDRESS"."CONTREF" ON "HOMCONCERN"."CONCREF" = "HOMADDRESS"."CONCREF" }
WHERE "HOMINVOLV"."PROJREF" = :proj AND "HOMNLPOST"."LANGREF" = :lang AND
"HOMINVOLV"."HISTORYREC" = '1' AND "HOMINVOLV"."RESTRICTEDACCESS" = '0' AND
"HOMADDRESS"."ADDRESSSTOP" = '0' AND "HOMNLPOST"."SENDNL" = '1' ORDER BY
"HOMCONT"."LASTNAME" ASC
This query which would have run before in prior setting is no longer working.
Error code: 1
pq_driver: [PGRES_FATAL_ERROR]ERROR: syntax error at or near "{"
LINE 1: ...HOMINVOLV"."INVREF", "HOMNLPOST"."AFRIGREET" FROM { OJ "publ...
^(caused by statement 'SELECT "HOMINVOLV"."PROJREF", "HOMNLPOST"."LANGREF",
"HOMINVOLV"."HISTORYREC", "HOMINVOLV"."RESTRICTEDACCESS",
"HOMADDRESS"."ADDRESSSTOP", "HOMNLPOST"."SENDNL", "HOMINVOLV"."TITLEREF",
"HOMINVOLV"."INITIALS", "HOMNLPOST"."PERSNAME", "HOMCONT"."LASTNAME",
"HOMCONCERN"."POSTHELD", "HOMCONCERN"."CONCERN", "HOMCONCERN"."BRANCHOFCONC",
"HOMADDRESS"."ADD1", "HOMADDRESS"."ADD2", "HOMADDRESS"."ADD3",
"HOMADDRESS"."ADD4", "HOMADDRESS"."ADD5", "HOMADDRESS"."ADD6",
"HOMNLPOST"."ENVELOPE", "HOMINVOLV"."INVREF", "HOMNLPOST"."AFRIGREET" FROM {
OJ "public"."HOMCONCERN" AS "HOMCONCERN" RIGHT OUTER JOIN "public"."HOMCONT"
AS "HOMCONT" RIGHT OUTER JOIN "public"."HOMINVOLV" AS "HOMINVOLV" RIGHT OUTER
JOIN "public"."HOMADDRESS" AS "HOMADDRESS" LEFT OUTER JOIN
"public"."HOMNLPOST" AS "HOMNLPOST" ON "HOMADDRESS"."ADDREF" =
"HOMNLPOST"."ADDREF" ON "HOMINVOLV"."INVREF" = "HOMNLPOST"."INVREF" ON
"HOMCONT"."CONTREF" = "HOMADDRESS"."CONTREF" ON "HOMCONCERN"."CONCREF" =
"HOMADDRESS"."CONCREF" } WHERE "HOMINVOLV"."PROJREF" = '1017' AND
"HOMNLPOST"."LANGREF" = 'English' AND "HOMINVOLV"."HISTORYREC" = '1' AND
"HOMINVOLV"."RESTRICTEDACCESS" = '0' AND "HOMADDRESS"."ADDRESSSTOP" = '0' AND
"HOMNLPOST"."SENDNL" = '1' ORDER BY "HOMCONT"."LASTNAME" ASC')
SELECT "HOMNLEMAIL"."LANGUAGE", "HOMINVOLV"."PROJREF", "HOMNLEMAIL"."SEND",
"HOMINVOLV"."RESTRICTEDACCESS", "HOMINVOLV"."HISTORYREC",
"HOMINVOLV"."TITLEREF", "HOMINVOLV"."INITIALS", "HOMCONT"."LASTNAME",
"HOMCONCERN"."POSTHELD", "HOMCONCERN"."CONCERN", "HOMCONCERN"."BRANCHOFCONC",
"HOMINVOLV"."INVREF", "HOMEMAIL"."emailadd", "HOMEMAIL"."emailstop",
"HOMNLEMAIL"."PERSNAMES", "HOMNLEMAIL"."AFRIGREET" FROM "HOMCONT" AS "HOMCONT"
RIGHT OUTER JOIN "HOMCONCERN" AS "HOMCONCERN" RIGHT OUTER JOIN "HOMINVOLV" AS
"HOMINVOLV" LEFT OUTER JOIN "HOMNLEMAIL" AS "HOMNLEMAIL" ON
"HOMINVOLV"."INVREF" = "HOMNLEMAIL"."INVREF" LEFT OUTER JOIN "HOMEMAIL" AS
"HOMEMAIL" ON "HOMNLEMAIL"."EMAILREF" = "HOMEMAIL"."EMAILREF" ON
"HOMCONCERN"."CONCREF" = "HOMINVOLV"."CONCREF" ON "HOMCONT"."CONTREF" =
"HOMINVOLV"."CONTREF" WHERE "HOMNLEMAIL"."LANGUAGE" = 'English' AND
"HOMINVOLV"."PROJREF" = 1017 AND "HOMNLEMAIL"."SEND" = '1' AND
"HOMINVOLV"."RESTRICTEDACCESS" = '0' AND "HOMINVOLV"."HISTORYREC" = '1' AND
"HOMEMAIL"."emailstop" = '0' ORDER BY "HOMCONT"."LASTNAME" ASC
Not potential to edit this data
On Monday 23 May 2011 20:01:16 you wrote:
> On Mon, May 23, 2011 at 9:53 AM, Dean le Roux <projserve@gmail.com> wrote:
> > postgres 8.3 to 8.4 Open office base 3.2 Ubuntu 9.04 to 10.04 (new
> > install)
> >
> > I recently upgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other
> > updates have been effected. I used webmin to restore the databases.
> >
> > Since migrating to Linux around 2006 we were successful in converting our
> > mdb
> > file to postgresql - only one glitch was a difference in -1 as YES. We
> > successfully used the systems with open office as a front end for the
> > last few
> > years. Until now - after the upgrade I can view data but not update data.
> >
> > Experience with sql is very limited as I have always used sql query
> > builders
> > over the years. The system has worked well with multiple tables, and in
> > the past there was no problems with sending sql statements to
> > postgresql.
> >
> > My problem in OOO 3.2 base (other front ends also) is that there is
> > continually a problem with not allowing queries to update data back to
> > postgresql.
> >
> > I believe something has changed perhaps in sql from 8.3 to 8.4, or I have
> > missed something with restoring the files.
>
> At minimum, we need to see the update statement that you are attempting to
> execute, preferably with any error message you receive.
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">OnMonday, May 23, 2011 9:53:47 am Dean le Roux wrote:<p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> postgres 8.3 to 8.4 Open
officebase 3.2 Ubuntu 9.04 to 10.04 (new<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> install)<p
style="-qt-paragraph-type:empty;margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Did the OO version change also?<p
style="-qt-paragraph-type:empty;margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> <p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> I
recentlyupgraded from Ubuntu 9.04 to Ubuntu 10.04. Security and other<p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> updates have been
effected.I used webmin to restore the databases.<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> <p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Since
migratingto Linux around 2006 we were successful in converting our<p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> mdb file to postgresql -
onlyone glitch was a difference in -1 as YES. We<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> successfully used the systems with open
officeas a front end for the last<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;">> few years. Until now - after the upgrade I can view data
butnot update<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">> data.<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Usually,
inBase, that indicates that it can not find a primary key.<p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">FYI:<p style="
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">Thebelow is redundant:<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">CONSTRAINT
"FINANCEDETAILS_pkey"PRIMARY KEY ("FINDETID"),<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">CONSTRAINT "FINANCEDETAILS_FINDETID_key"
UNIQUE("FINDETID")<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">From the docs:<p style="
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">http://www.postgresql.org/docs/8.4/interactive/sql-createtable.html<p
style="-qt-paragraph-type:empty;margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">"Technically, <span style="
font-family:'CourierNew,courier';">PRIMARY KEY</span> is merely a combination of <span style=" font-family:'Courier
New,courier';">UNIQUE</span>and <span style=" font-family:'Courier New,courier';">NOT NULL</span>, but identifying a
setof columns as primary key also provides metadata about the design of the schema, as a primary key implies that other
tablescan rely on this set of columns as a unique identifier for rows. "<p style="-qt-paragraph-type:empty;
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;"><pstyle=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Experience with sql is very limited as I
havealways used sql query<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;">> builders over the years. The system has worked well with
multipletables,<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">> and in the past there was no problems with sending sql statements to<p style="
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;">>postgresql.<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;">> <p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> My problem in OOO 3.2
base(other front ends also) is that there is<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> continually a problem with not allowing
queriesto update data back to<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;">> postgresql.<p style="-qt-paragraph-type:empty;
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;"><pstyle=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">What are you using to connect to the database JDBC, ODBC, other?<p
style="-qt-paragraph-type:empty;margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> <p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> I
believesomething has changed perhaps in sql from 8.3 to 8.4, or I have<p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> missed something with
restoringthe files.<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px;
margin-left:0px;margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Did you do a full restore or
selective?<pstyle="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> <p style="-qt-paragraph-type:empty;
margin-top:0px;margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;
-qt-user-state:0;"><pstyle=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">> <p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">> Any assistance offered will be
appreciated.<pstyle="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px;
-qt-block-indent:0;text-indent:0px; -qt-user-state:0;"><p style=" margin-top:0px; margin-bottom:0px; margin-left:0px;
margin-right:0px;-qt-block-indent:0; text-indent:0px; -qt-user-state:0;">-- <p style=" margin-top:0px;
margin-bottom:0px;margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;">Adrian
Klaver<pstyle=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0;
text-indent:0px;-qt-user-state:0;">adrian.klaver@gmail.com
I installed the recommended JDBC driver. Set it up to connect using Open office. Still need to test to see how the queries build now, but problem is that the access to the database is dramatically slower than using the sdbc. Is this to be expected. thanks. On 05/24/2011 07:58 AM, Dean le Roux wrote: > Apologise for missing those other questions. > > Not sure if it is normal for most queries to not allow for update? > > So, when using a prior form designed in OOO3, which allows editing of > data: > pq_baseresultset: row index out of range, allowed is 0 to -1, got 0 > In the postgresql dbase a record is added. So the UI is reporting a problem, but the record is inserted anyway? > > Using extension manager postgresql-sdbc-0.7.6.a.zip That could be part of the problem.The Postgres SDBC driver is Beta quality at best. Per the known issues(http://dba.openoffice.org/drivers/postgresql/index.html#features): Data modifcation Modification of data in tables via the UI (e.g. via the beamer window) is only possible, when your table has a primary key and the primary key is part of the used select statement (otherwise the OOo framework has no possibility to find the row again to write the modification). Updateable resultsets Updateable resultsets are currently implemented for selects on simple tables only. Resultsets containing data from multiple tables raise errors in case a modification is attempted. #i30059# Updates may fail on tables with non-primary-indexes I have had better luck using the appropriate JDBC driver for the Postgres version(http://jdbc.postgresql.org/download.html). > > I never bothered to check the database structure, time constraints, but > with > this problem, I am seeing that many foreign keys are not listed. In > MsAccess > we used VBA and most times enforced referential integrity through > relationships, etc. So I am working on this to see if that is a problem. > We > have 88 tables, but there are a few mission critical, the other data moves > slowly, Foreign keys should not cause what you are seeing. As you say they are there to enforce referential integrity. What is important is that each table you want to update have a Primary Key. > > I have most times used webmin to backup postgres db, and used the same to > do > the restore after the upgrade. I first create the database in webmin, and > then > restore the database, using default settings. Where there any errors when you did the restore? > > Hope that answers things. Appreciate your help thus far. > > > On Tuesday 24 May 2011 16:16:58 you wrote: >> On Monday, May 23, 2011 10:41:09 pm you wrote: >>> Yes, to 3.2, but it seem that views built in phppgadmin also don't allow >>> for data update >> >> You are going to have to give more detail:) What do the Postgres logs say >> when you try to update? In addition I asked a couple of other questions >> in >> my previous email. >> >> What are you using to connect to the database, JDBC,ODBC, other? >> What sort of restore did you do, full or selective ? -- Adrian Klaver -- View this message in context: http://postgresql.1045698.n5.nabble.com/problem-with-update-data-sets-from-front-ends-8-4-Ubuntu-10-04-tp4419558p4445490.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com.