[freeside] Freeside not SQL compliant?

Ivan Kohler ivan at sisd.com
Wed Nov 3 10:07:55 PST 1999


On Sat, Oct 23, 1999 at 09:41:17PM -0400, Stephen Amadei wrote:
> On Thu, 21 Oct 1999, Ivan Kohler wrote:
> 
> I probably should move this to the devel list, but...

Good idea; I've done so.  I'm Cc:'ing the regular list for _this message
only_, so folks searching the list archive later on know where the
discussion moved. 

> > Depending on the radius attributes you decide to track with Freeside,
> > column names can get really long (especially in the part_svc table), i.e. 
> > 'svc_acct__radius_Attribute_Name_flag'
> 
> After my translation: 'sa__r_1_f'.  Then dig in the radius table for
> attribute 1.  I know I loose alot of readability, but it seems to leave
> most of the Freeside functionality intact.

Seems like the best that can be done; I agree that strict SQL complience
is preferred.

> > Good luck!  I'd certainly be interested in including these changes into
> > the main package, and, time permitting, could help with some of the
> > difficult bits.
> 
> Well, I'm still just starting... some parts have looked pretty bad, but
> others are nice, quick changes... but I have run into a bit of a wall...
> 
> Is is really necessary to built an index for table 'cust_svc' on column
> 'svcnum', since an implicit index is created when you make 'svcnum' the
> primary key (at least in DB2, I'm not sure if MySQL does this)?  In DB2,
> you cannot create an index if an identical index already exists.

Hmm.  Yes, you should be able to remove that from fs-setup.

> I'm still trying to decipher the big %table thing in fs-setup... ;-)

Have you checked out FS::dbdef and FS::dbdef_table, etc.?  Their manpages
might help?

-- 
Ivan Kohler <ivan at sisd.com> - finger for PGP key - <moc.dsis at navi> Relhok Navi
Open-source billing and administration for ISPs - http://www.sisd.com/freeside
20 4,16 * * * saytime # please don't be surprised if you find me dreaming too



More information about the freeside-devel mailing list