Hi all,
I have to follow up on my own mail:
Joerg Bruehe wrote:
[[...]]
For tabular form, try along these lines (untested):
SELECT MIN(id), email, id
FROM addressbook
WHERE id MIN(id)
GROUP BY email
HAVING COUNT(*) 1
I cannot explain what made me write that, other than lack
(Sorry if this is a duplicate post, email issues w/multiple accts)
I have a MacBook Leopard OS 10.5.1 2 GB RAM. I've got a good amount of
knowledge of computer systems, but haven't setup or worked with mySQL
before. (usually use it preinstalled on my hosting service). I
downloaded the package and
On Dec 13, 2007 12:11 PM, Al [EMAIL PROTECTED] wrote:
(Sorry if this is a duplicate post, email issues w/multiple accts)
I have a MacBook Leopard OS 10.5.1 2 GB RAM. I've got a good amount of
knowledge of computer systems, but haven't setup or worked with mySQL
before. (usually use it
On Wed, Dec 12, 2007 at 05:11:43PM -0800, Ed Reed wrote:
I've found a glaring problem with the latest ODBC connector. Data
types have been changed and data is no longer being read correctly.
That's not quite correct -- data types are now actually being read
correctly. They were wrong before,
Hi, i hit a weird behavior:
select date(null); #result is null
select if(date(null) is null, 1, 2); #result is 2 (not null)
select if(date(null) is not null, 1, 2); #result is 1
I use mysql version 5.0.32-Debian_7etch1-log.
Is this a bug and if not, can anyone explain why?
Thanks,
Daniel
--
Hi,
On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] wrote:
Hi, i hit a weird behavior:
select date(null); #result is null
select if(date(null) is null, 1, 2); #result is 2 (not null)
select if(date(null) is not null, 1, 2); #result is 1
I use mysql version 5.0.32-Debian_7etch1-log.
Baron Schwartz wrote:
Hi,
On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] wrote:
Hi, i hit a weird behavior:
select date(null); #result is null
select if(date(null) is null, 1, 2); #result is 2 (not null)
select if(date(null) is not null, 1, 2); #result is 1
I use mysql version
On Dec 13, 2007 4:18 PM, Daniel Mikic [EMAIL PROTECTED] wrote:
Baron Schwartz wrote:
Hi,
On Dec 13, 2007 3:53 PM, Daniel Mikic [EMAIL PROTECTED] wrote:
Hi, i hit a weird behavior:
select date(null); #result is null
select if(date(null) is null, 1, 2); #result is 2 (not null)
select
Is it possible for a trigger to test the data to be inserted and if it doesn't
meet specific criteria not insert the data at all?
I have an application that writes a lot of data to my table. I don't have
control over this application and it writes a lot more data then I need. So I'd
like to
