On Fri, 11 Jul 2003 03:58 pm, Ulrich Walcher wrote: > > When I am trying to start the radius server and do accounting ith > > postgres I get some errors when the values are being inserted: > > > > ERROR: "Bad numeric input format '' > > --snip-- > > > CalledStationId VARCHAR(10) DEFAULT '' NOT NULL, > > CallingStationId VARCHAR(10) DEFAULT '' NOT NULL, > > Some time ago I think I had this problem, too. > Anyway, the given defaults for CalledStationId and CallingStationId with > VARCHAR(10) have been way too low for my needs. > After altering these two fields to VARCHAR (18) it worked... > May and may not be the solution...
Yes. You are right. For my voip billing schema (which is in CVS in the billing directory) I use the following. This should allow a full international telephone number to fit in there.. I will fix the standard DB schemas now.. CalledStationId VARCHAR(50) DEFAULT '' NOT NULL, CallingStationId VARCHAR(50) DEFAULT '' NOT NULL, Thanks for pointing this out. Look like I need to spend some time backporting my fixes for VoIP billing to the standard schemas for all the databases. On a side not, is there any reason why we have NOT NULL set on the field types? Will this break something if a db returns a NULL? IMHO it is a waste space and processor to insert "" into a field when you could just leave it NULL. CCing this to -devel.. -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
