Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5UL8la07454 for ; Sat, 30 Jun 2001 17:08:48 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 79482 for ; Sat, 30 Jun 2001 14:08:45 -0700 From: "Josh Berkus" Subject: Date validation? To: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Sat, 30 Jun 2001 14:08:45 -0700 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_===79482====davinci.ethosmedia.com===_" X-Archive-Number: 200106/477 X-Sequence-Number: 3780 This is a multi-part MIME message --_===79482====davinci.ethosmedia.com===_ Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit Folks, Is there any PgSQL or PL/pgSQL function which validates dates? I've tried ISFINITE and CAST ... AS DATE but these suffer fatal errors if the date isn't valid (e.g. '2001-06-31'). I need a test I can trap inside a PL/pgSQL function. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco --_===79482====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===79482====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===79482====davinci.ethosmedia.com===_ Content-Type: text/plain Content-Disposition: attachment; filename="" Content-Transfer-Encoding: base64 DQo= --_===79482====davinci.ethosmedia.com===_--