Forum OpenACS Development: Error ref_timezones-create from HEAD

I know it's supposed to be my HEADache to install from HEAD, but I couldn't resist. :)

Anyone have any clue on this one? I get a similar error (bla bla does not exist) when I try to install new-portal as well.
I am using Postgresql 7.3 (could it be it?).

psql:ref-timezones-create.sql:60: ERROR:  Relation 'timezones' already exists
psql:ref-timezones-create.sql:70: ERROR:  Function acs_reference__new("unknown", "unknown", "unknown", "unknown", timestamptz) does not exist
    Unable to identify a function that satisfies the given argument types
    You may need to add explicit typecasts
psql:../common/ref-timezones-data.sql:7: ERROR:  Cannot insert a duplicate key into unique index timezones_tz_id_pk
psql:../common/ref-timezones-data.sql:8: ERROR:  Cannot insert a duplicate key into unique index timezones_tz_id_pk
psql:../common/ref-timezones-rules.sql:275: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:729: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:1267: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:1814: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:2447: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:3261: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:4119: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:5328: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:6180: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:7004: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:7432: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:8318: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:9083: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:9938: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:10624: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:11145: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:11602: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:12192: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:12757: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:13823: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:14295: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:14909: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:15792: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:16798: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:17816: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:18985: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:20492: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:21294: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:21994: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:22988: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:24441: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:25963: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:27301: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:28393: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:28763: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:28919: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:29235: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:31083: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:31959: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:32062: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:32095: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:32590: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:33962: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:35207: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:35790: WARNING:  COMMIT: no transaction in progress
psql:../common/ref-timezones-rules.sql:36045: WARNING:  COMMIT: no transaction in progress

    invoked from within
"db_source_sql_file -callback $callback $path/$file_path"
    (procedure "apm_package_install_data_model" line 32)
    invoked from within
"apm_package_install_data_model -callback $callback -data_model_files $data_model_files $spec_file_path"
    (procedure "apm_package_install" line 19)
    invoked from within
"apm_package_install  -enable=$enable_p  -install_path $install_path  -callback apm_ns_write_callback  -load_data_model  -data_model_files $data_model_..."
    ("foreach" body line 47)
    invoked from within
"foreach pkg_info $pkg_install_list {
    set spec_file [pkg_info_spec $pkg_info]
    if { [catch {
    array set version [apm_read_package_info_file $spe..."
    ("uplevel" body line 35)
    invoked from within
"uplevel {
          ad_page_contract {

    Installs the packages.

    @author Bryan Quinn (mailto:bquinn@arsdigita.com)
    @creation-date Mon Oct  9 00:22:31..."
    (procedure "code::tcl::/web/mysite/packages/acs-admin/www/apm/packages-i..." line 2)
    invoked from within

/Håkan

Collapse
Posted by Jon Griffin on
Timezones will absoultly not work with head because of PG's lame insistence on breaking things. It will work by release of 4.7,but for now if you really want to, change the timestamp to timestamptz (IIRC).
Collapse
Posted by Tom Jackson on

I am working on an improvement to my query-writer package to allow it to create the __new, etc pl code using only the datamodel and a few hints, if necessary. The first visible result is a data model browser. I noticed that all date types are actually stored as timestampz types, even though the table create uses timestamp.

Collapse
Posted by Don Baccus on
This is the problem.  They are now stored WITHOUT timezone information in PG 7.3.  This change is not transparent to the code.

In order for us to support both PG 7.2 and PG 7.3 - not to mention dump-restore upgrades from 7.2 to 7.3 - we need to change all "timestamp" decls in the toolkit to "timestamptz".

Grrr...