octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #44345] Database package: Error connecting to


From: anonymous
Subject: [Octave-bug-tracker] [bug #44345] Database package: Error connecting to older Postgresql
Date: Sun, 22 Feb 2015 23:15:19 +0000
User-agent: Mozilla/5.0 (X11; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0

URL:
  <http://savannah.gnu.org/bugs/?44345>

                 Summary: Database package: Error connecting to older
Postgresql
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 22 Feb 2015 11:15:17 PM UTC
                Category: Octave Forge Package
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

I tried to connect to postgresql 8.1.23 (Current version on RHEL 5)

Connection fails with:
"
octave:14> et.db.pgconn = pq_connect(con_str);
error: octave_pq_fill_base_types: fatal error: ERROR:  column "typarray" does
not exist

error: could not read types
error: called from:
error:   /usr/share/octave/packages/database-2.3.0/pq_connect.m at line 112,
column 8
"

The error happens here:
http://sourceforge.net/p/octave/code/HEAD/tree/trunk/octave-forge/main/database/src/pq_connection.cc#l212

Checking through the Postgresql docs, I found:
"
The old naming convention is still honored when possible, but application code
should no longer depend on it. Instead use the new pg_type.typarray column to
identify the array data type associated with a given type.
"
(http://www.postgresql.org/docs/8.3/static/release-8-3.html)

Ok, they started with typearray at Postgresql 8.3...
RHEL 5 is still supported until March 31, 2017, but they won't upgrade
anything except for critical issues.

So, would it be possible to catch this error and output a message like
"Postgres minimum supported version is 8.3", or handle the error? (=not
relying on typearray)

Claudius




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44345>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]