[freeside] postgresql error : ExecAppend: Fail to add null value in not null attribute

ivan at 420.am ivan at 420.am
Tue May 6 19:49:55 PDT 2003


On Tue, May 06, 2003 at 10:41:04PM -0400, Timothy M. Butkiewicz wrote:
> 
> Prior to 1.4.1rc1 I was at 1.4.1beta6.

Forgive my skepticism, but your errors indicate a schema from a
development snapshot before 1.4.0 release.  User-level support tracking
development snapshots isn't really something I have the available time
to provide, sorry.

> Was there that much diff in the schema?  between these versions?

The schema does not change in a major version (1.4.0->1.4.1->1.4.x).
Your errors indicate a schema from before 1.4.0.

-- 
_ivan


> 
> 
> Quoting ivan at 420.am:
> 
> > You upgraded from a prerelease development snapshot prior to
> > 1.4.0 and did not make the necessary schema changes.
> > 
> > I attempt to maintain schema compatibility across major versions
> > (1.4.0->1.4.1 etc.) but you should be prepared to track schema changes
> > if you're going to run development snapshots.
> > 
> > You might try the the CVS Attic for upgrade instructions
> > <http://www.sisd.com/cgi-bin/viewcvs.cgi/freeside/Attic/>.
> > 
> > Good luck.
> > 
> > -- 
> > _ivan
> > 
> > 
> > On Tue, May 06, 2003 at 11:50:02AM -0400, Timothy M. Butkiewicz wrote:
> > > 
> > > Running:
> > > Postgresql 7.2.1
> > > Apache 1.3.27
> > > Redhat 7.2
> > > Freeside 1.4.1rc1
> > > 
> > > Recently updated Freeside to 1.4.1rc1 as well as Postgresl to 7.2.1 (used 
> > > pg_dump etc)
> > > 
> > > First noticed that there was an issue during the freeside-daily cron job
> > run. 
> > > When customers were being billed, an invoice would generate, but the
> > account 
> > > would not be paid.
> > > 
> > > When manually running "Bill Now", the following error is displayed:
> > > WARNING: Event run but database not updated - error inserting
> > cust_bill_event, 
> > > invnum #20483, eventpart 2: ERROR: ExecAppend: Fail to add null value in
> > not 
> > > null attribute eventnum 
> > > 
> > > I have checked the postgresql Db and the eventnum field is not read-only.
> > Nor 
> > > was it set to read-only in the dump. 
> > > 
> > > During various updates throught Freeside, error are returned when trying to
> > 
> > > update the database - 
> > > 
> > > When modifying a DNS entry
> > > ERROR: value too long for type character varying(80) 
> > > (Apache reports - DBD::Pg::st execute failed: ERROR:  value too long for
> > type 
> > > character varying(80) at /usr/lib/perl5/site_perl/5.6.1//FS/Record.pm line
> > 689.)
> > > 
> > > Any help would be greatly appreciated.
> > > 
> > > ----------------------------------------
> > > This mail sent through cyberMIND webMAIL
> > > 	webmail.cybermind-usa.net
> > 
> > -- 
> > _ivan
> > 
> 
> 
> +---------------------------- 
> Timothy M. Butkiewicz 
>  Director of Office Technologies 
>  cyberM.I.N.D. 
>  877.373.6680 x 20 
>  269.373.6680 x 20 
>  www.cybermind.biz 
>  www.cybermind-usa.net 
> 
> Domain Name Sale!!
> .COM, .NET and .ORG registrations for $19.95 per year!
> .US and .BIZ are on sale for $8.95 per year! 
> Transfers are only $13.95 and include a 1 year extension!
> http://www.cybermind-usa.net/dns/
> 
> ----------------------------------------
> This mail sent through cyberMIND webMAIL
> 	webmail.cybermind-usa.net

-- 
_ivan



More information about the freeside-users mailing list