Re: [eGroupWare-developers] NOT NULL database errors with egroupware 0.99.004 and postgresql 7.3.2

[Greg H. <shr...@be...>]

Michael - A number of the applications have been found to be 
incompatible with PostgreSQL 7.3.x, due to some of the changes that 
occured in that database's recent releases.  A lot of the eGW code has 
already been fixed in the CVS tree, but we would appreciate any bug 
reports you can provide, to make sure we don't miss anything for the 
upcoming release.  You can file these through the project page on 
SourceForge.net.

Thanks!
-g

Michael Stern wrote:
> I am getting some rather odd errors using some of the modules.  All of
> them seem to revolve around a common theme:  an attempt to write null
> data to a NOT NULL field.  I'll include an example here, and hopefully
> it helps to find a solution:
> 
> Comics
> Database error: Invalid SQL: insert into phpgw_comic (comic_owner)
> values ('3')
> PostgreSQL Error: 1 (ERROR: ExecInsert: Fail to add null value in not
> null attribute comic_list )
> 
> After this, I tried some administrative functions thinking that the
> tables were not "seeded" with required "starter" data.
> 
> Global Comic Options.   Made my selection and clicked Submit.  Result:
> 
> Database error: Invalid SQL: update phpgw_comic_admin set
> admin_imgsrc='0', admin_rmtenabled='', admin_censorlvl='2',
> admin_coverride='1', admin_filesize='120000'
> PostgreSQL Error: 1 (ERROR: pg_atoi: zero-length string )
> 
> Next stop on our world tour is Global Comics.  Everything seemed fine
> there.
> 
> Personally, I could live without this module, but similar errors are
> fouling my attempts at integrating the email modules.  These are
> absolutely key to my rollout of this project.  The same errors also
> occur with other modules that I hadn't initially planned on including,
> but would like to retain the ability to do so if they are requested.
> 
> I have a feeling that if we can find out what the problem with the
> comics module, the others will probably be easily resolved.
> 
> My gut feeling tells me that I should have gone with MySQL.
> Unfortunately, I have applications that require functionality in
> PostgreSQL that MySQL does not provide.  I am not against running two
> database servers, but that doesn't sound like a very elegant solution.
> 
> Please advise.
> 
> P.S.  I will continue searching for a solution on your website.  If you
> have already addressed this issue, my apologies.
> 
> _________________________________________________________________
> Instant message in style with MSN Messenger 6.0. Download it now FREE!  
> http://msnmessenger-download.com
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> SourceForge.net hosts over 70,000 Open Source Projects.
> See the people who have HELPED US provide better services:
> Click here: http://sourceforge.net/supporters.php
> _______________________________________________
> eGroupWare-developers mailing list
> eGr...@li...
> https://lists.sourceforge.net/lists/listinfo/egroupware-developers