On Tue, 2 Mar 1999, Mike McCauley wrote:
> The bahaviour you are seeing is because the normal behaviour of
> "integer-date" is to make an SQL date/time with 0 seconds.
>
> Its this way to be compatible with some other more braindead SQLs.
Ahh, okay. Hmmph. Make the braindead ones use the formatted-date type,
and give a break to people who use non-braindead stuff. *grin*
> If you are at Radiator Revision 2.13, look at the new formatted-date type in
> AcctColumnDef, where you can build an SQL date in any format you like.
Too late. (: I am at 2.13; it was released a couple of days prior to
me burning the master disk for our radius server...and it passed basic
testing so I threw caution to the wind and burned my production cd with
your new release rather than the older one. [all critical software on
my server is burned on cd's which are mounted at appropriate parts of
my filesystem (am running Linux). Stops scriptkiddies cold when they
can't replace my binaries and libs and critical configs/cronjobs.]
BTW, I can see where you're coming from when you say that y'all's opinion
is that everybody of moderate size or better oughta be using SQL. Heck,
I'm a *tiny* sized ISP (~350 customers), and a handful of days ago
switched to my new server based on Linux/Radiator/Postgres/ApacheSSL.
This stuff is slicker than eel shit, I'm tellin' ya. I'm learning more
about everything I do simply because AnyNumberIWant is a quick sql
select command. This is truly The Way It Is Supposed To Be.
[and Mike, if you wanna use the slicker than eel shit comment as
an endorsement from 'a rural Virginia ISP', feel free. *cackle*]
Lon Stockton
MoonStar
===
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
