--- Forwarded mail from [EMAIL PROTECTED] Date: Sun, 11 Jun 2000 08:10:16 +1000 (EST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: BOUNCE [EMAIL PROTECTED]: Non-member submission from ["Robert Mann" <[EMAIL PROTECTED]>] >From mikem Sun Jun 11 08:10:10 2000 Received: by oscar.open.com.au (8.9.0/8.9.0) id IAA20013 for [EMAIL PROTECTED]; Sun, 11 Jun 2000 08:10:09 +1000 (EST) >Received: from frank.easyway.com (adsl-63-199-67-170.dsl.bkfd14.pacbell.net [63.199.67.170]) by perki.connect.com.au with SMTP id HAA16953 (8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Sun, 11 Jun 2000 07:55:01 +1000 (EST) Received: from frank.easyway.com (adsl-63-199-67-170.dsl.bkfd14.pacbell.net [63.199.67.170]) by perki.connect.com.au with SMTP id HAA16953 (8.8.8/IDA-1.7 for <[EMAIL PROTECTED]>); Sun, 11 Jun 2000 07:55:01 +1000 (EST) Received: (qmail 20951 invoked from network); 10 Jun 2000 21:59:16 -0000 Received: from adsl-63-199-67-174.dsl.bkfd14.pacbell.net (HELO rdm) (63.199.67.174) by adsl-63-199-67-170.dsl.bkfd14.pacbell.net with SMTP; 10 Jun 2000 21:59:16 -0000 Message-ID: <001001bfd326$5d97a320$[EMAIL PROTECTED]> From: "Robert Mann" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: Duplicate Accounting Records with MySQL Date: Sat, 10 Jun 2000 14:53:52 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4029.2901 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4029.2901 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01BFD2EB.B1280240" This is a multi-part message in MIME format. ------=_NextPart_000_000D_01BFD2EB.B1280240 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable What is the easiest way to address this problem with MySQL. I am = working on a companies Radiator server that uses MySQL as its database = server for accounting and there are many duplicate records. In MS SQL = it was easy as I could use a constraint that would prevent it from = happening but it is my understanding that MySQL does not have this = functionality. If I am wrong please right me and give me an example. = If I am right then how do you work around this problem? Thank you, Robert Mann Senior Systems Administrator OneMain.com ------=_NextPart_000_000D_01BFD2EB.B1280240 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-1"> <META content=3D"MSHTML 5.50.4030.2400" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT face=3DArial size=3D2>What is the easiest way to address this = problem=20 with MySQL. I am working on a companies Radiator server that uses = MySQL as=20 its database server for accounting and there are many duplicate = records. =20 In MS SQL it was easy as I could use a constraint that would = prevent=20 it from happening but it is my understanding that MySQL does not have = this=20 functionality. If I am wrong please right me and give me an = example. =20 If I am right then how do you work around this problem?</FONT></DIV> <DIV><FONT face=3DArial size=3D2></FONT> </DIV> <DIV><FONT face=3DArial size=3D2>Thank you,</FONT></DIV> <DIV><FONT face=3DArial size=3D2><BR>Robert Mann<BR>Senior Systems=20 Administrator<BR>OneMain.com</FONT></DIV></BODY></HTML> ------=_NextPart_000_000D_01BFD2EB.B1280240-- ---End of forwarded mail from [EMAIL PROTECTED] -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. Ltd Unix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8, 2000, NT, MacOS X === 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.