Hello Hugh,
I agree, that it's not portable to all SQL platforms.. but what I don't
understand is why you can't put it in your AddQuery (in the radius config
file).. I mean, IF you are capable of using it, I think that you should be
able to do it in a proper way, by using it in your AddQuery, and not by
changing it in the source of the package...
Just my 0.02 cents ,-)
-Andy
> -----Original Message-----
> From: Hugh Irvine [mailto:[EMAIL PROTECTED]]
> Sent: Friday, November 24, 2000 12:25 AM
> To: Andy De Petter; Carlos Canau
> Cc: Radiator Mailing
> Subject: RE: (RADIATOR) SessionDatabase SQL problem
>
>
>
> Hello Andy, Hello Carlos -
>
> On Fri, 24 Nov 2000, Andy De Petter wrote:
> > I've been around that problem, by changing the source of the Radiator
> > package:
> >
> > REPLACE INTO instead of INSERT INTO, concerning the sessiondatabase ...
> >
> > Don't know how you could get around that problem on a more
> "decent" way...
> > changing the "AddQuery" in the config, doesn't change much .. the insert
> > into is hardcoded in the package.
> >
>
> As Mike says, REPLACE INTO is not portable across all databases,
> that is why
> INSERT INTO is used.
>
> :-(
>
> regards
>
> Hugh
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
> -
> Nets: internetwork inventory and management - graphical, extensible,
> flexible with hardware, software, platform and database independence.
>
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
