[Phpgroupware-tracker] [bug #6259] Upgrade from 0.9.14.007 to latest CVS failed

[nobody]

=================== BUG #6259: LATEST MODIFICATIONS ==================
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=6259&group_id=509

Changes by: Chris Weiss <address@hidden>
Date: Thu 10/30/2003 at 20:30 (America/Chicago)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | cw                        | skwashd


------------------ Additional Follow-up Comments ----------------------------
Well, I was assigned i'm sure cause Dave thought this was related to the ERROR 
log changes I imported, but it's not.  This is a problem in the pgsql schema 
proc and is also much earlier than the error log code anyway :P



Since I have not a pgsql server, nor do I know pgsql quirks I ask to have this 
reassigned to someone that does.



To help though, since this step changes a varchar(255) to an int(4) I wonder if 
any data in your table in the 'lo' column was not really an int or null.  I 
know we have people using pgsql and I think at least one did an upgrade, so I 
wonder if it's odd data related.





=================== BUG #6259: FULL BUG SNAPSHOT ===================


Submitted by: mexico                  Project: phpGroupWare                 
Submitted on: Thu 10/30/2003 at 17:48
Category:  API - Setup                Bug Group:  0.9.16RC1                 
Severity:  5 - Major                  Priority:  High                       
Resolution:  None                     Assigned to:  skwashd                 
Status:  Open                         Component Version:  CVS               
Platform Version:  Linux - Debian     Reproducibility:  Every Time          

Summary:  Upgrade from 0.9.14.007 to latest CVS failed

Original Submission:  System info:

Linux Debian sid

Apache 1.3.28

PHP 4.3.3

PostgreSQL 7.3.4

phpgroupware 0.9.14.512 (latest CVS update)





After installing latest CVS version (0.9.14.512, which is working fine if 
installed on clear database), I tryied to upgrade from old version 
(0.9.14.007). In Setup, when selected Upgrade, upgrade halted with error 
message:



Database error: Invalid SQL: INSERT INTO phpgw_access_log () VALUES ()

PostgreSQL Error: 1 (ERROR: parser: parse error at or near ")" at character 31 )



when activate debug in setup/index.php,

I've got a messages, which ends with:



process->upgrade(): appname: phpgwapi

process->upgrade(): currentver: 0.9.14.505

process->upgrade(): targetver: 0.9.14.512

process->upgrade(): status: R

process->upgrade(): checking: 0.9.14.505

process->upgrade(): function: phpgwapi_upgrade0_9_14_505

process->upgrade(): running phpgwapi_upgrade0_9_14_505

DropSequenceForTable: phpgw_access_log

GetSequenceForTable: phpgw_access_log

DropSequenceForTable: phpgw_access_log

GetSequenceForTable: phpgw_access_logDatabase error: Invalid SQL: INSERT INTO 
phpgw_access_log () VALUES ()

PostgreSQL Error: 1 (ERROR: parser: parse error at or near ")" at character 31 )



after this, I look in database, and I found missing table phpgw_acces_log, 
there is only phpgw_acces_log_tmp with old structure. After trying read/debug 
PHP code, it's look that error is in function _CopyAlteredTable in 
class.schema_proc_pgsql.inc.php in phpgwapi (not create values for SQL 
statement).



At this time, I can't debug php code, maybe tomorow for next info.

Follow-up Comments
*******************

-------------------------------------------------------
Date: Thu 10/30/2003 at 20:30       By: cw
Well, I was assigned i'm sure cause Dave thought this was related to the ERROR 
log changes I imported, but it's not.  This is a problem in the pgsql schema 
proc and is also much earlier than the error log code anyway :P



Since I have not a pgsql server, nor do I know pgsql quirks I ask to have this 
reassigned to someone that does.



To help though, since this step changes a varchar(255) to an int(4) I wonder if 
any data in your table in the 'lo' column was not really an int or null.  I 
know we have people using pgsql and I think at least one did an upgrade, so I 
wonder if it's odd data related.




CC list is empty


No files currently attached


For detailed info, follow this link:
http://savannah.gnu.org/bugs/?func=detailbug&bug_id=6259&group_id=509

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