bugphpGroupWare - Bugs: bug #3475, so_sql has error for date...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #3475: so_sql has error for date postgresql fields when using save function

Submitted by:  Johnson <jecinc>
Submitted on:  Mon 05 May 2003 04:50:48 PM UTC  
 
Item Group: NoneCategory: eTemplates
Severity: 3 - NormalPriority: 5 - Normal
Status: NonePrivacy: Public
Assigned to: Caeies <Caeies>Open/Closed: Open
Component Version: NoneOperating System: None
Reproducibility: NonePlanned Release: None
Fixed Release: 

Wed 14 May 2003 03:13:03 AM UTC, comment #1:

Looks like you prepared for this since there is an $empty_on_write = "NULL"; near the top of the so_sql class but the save function uses $this->empty_on_write that doesn't seem to be set equal to "NULL"

I added $this->empty_on_write = "NULL"; immediately above $cols .= ($cols ? ',' : '') . $db_col; and the save started to work for me.

I realize this is a hack but should help you find where the problem really is.

Would this also solve postgresql 7.3 bugs for fields not liking '' for apps using so_sql? I think it would

Johnson <jecinc>
Mon 05 May 2003 04:50:48 PM UTC, original submission:

Empty date fields are set to '' but postgresql returns error

Postgresql wants null date values set to null (not '')

Johnson <jecinc>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 2 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Sun 06 Jun 2004 11:26:32 PM UTCskwashdAssigned toNone=>Caeies
Tue 20 Jan 2004 12:13:43 PM UTCpowerstatAssigned toInvalid User ID=>None

Back to the top


Powered by Savane 3.1-cleanup1