Re: avoiding use of Nulls

2009-03-13 Thread Arthur Fuller
On Fri, Mar 13, 2009 at 3:20 PM, Andy Wallace wrote: > ggghh > > > mich...@j3ksolutions.com wrote: > >> On Fri, 13 Mar 2009, mich...@j3ksolutions.com wrote: >>> >>> Explanation(5): The more you understand how the database is to be used, and the

Fwd: avoiding use of Nulls

2009-03-13 Thread Arthur Fuller
Exactly the point. Michael, NULL *is* information. It means "unknown" and that is in itself useful information. A common example: A new employee is hired but which department she will work in is unknown. So the data entry person enters all the known information and leaves the rest until it has be

Re: avoiding use of Nulls

2009-03-13 Thread PJ
mich...@j3ksolutions.com wrote: >> On Fri, 13 Mar 2009, mich...@j3ksolutions.com wrote: >> >> >>> Explanation(5): The more you understand how the database is to be used, >>> and the more complexity and thought you put into your database design, >>> the >>> less complex it will be to retrieve r

Re: Getting single results per (left) record with INNER JOIN

2009-03-13 Thread Nigel Peck
Nigel Peck wrote: ... My query is: SELECT `People`.`person_id`, `People`.`name`, FROM `People` INNER JOIN `Person_postal_addresses` ON `Person_postal_addresses`.`person_id` = `People`.`person_id` WHERE `People`.`name` REGEXP 'example' OR `Person_postal_addresses`.

Re: avoiding use of Nulls

2009-03-13 Thread Andy Wallace
ggghh mich...@j3ksolutions.com wrote: On Fri, 13 Mar 2009, mich...@j3ksolutions.com wrote: Explanation(5): The more you understand how the database is to be used, and the more complexity and thought you put into your database design, the less co

Getting single results per (left) record with INNER JOIN

2009-03-13 Thread Nigel Peck
I'm hoping someone can point me in the right direction for what I need, to save me trawling through books and Google when I don't know what I'm looking for. I'm using an INNER JOIN to query a table that has a one-to-many relationship with the table in my FROM clause, but I only want one res

Re: avoiding use of Nulls (was: The <=> operator)

2009-03-13 Thread michael
> On Fri, 13 Mar 2009, mich...@j3ksolutions.com wrote: > >> Explanation(5): The more you understand how the database is to be used, >> and the more complexity and thought you put into your database design, >> the >> less complex it will be to retrieve reliable information out of it. >> Furthermore,

Re: avoiding use of Nulls (was: The <=> operator)

2009-03-13 Thread Thomas Spahni
On Fri, 13 Mar 2009, mich...@j3ksolutions.com wrote: Explanation(5): The more you understand how the database is to be used, and the more complexity and thought you put into your database design, the less complex it will be to retrieve reliable information out of it. Furthermore, (and this is pr

Re: Select query locks tables in Innodb

2009-03-13 Thread Perrin Harkins
2009/3/12 Carl : > I am still a little puzzled about how we could have a relatively large set > of records (100,000+) and yet not cause any table to be locked as the server > has only 8GB of memory. What's the relationship you're implying between memory and locking? Multi-version concurrency doesn

Re: avoiding use of Nulls (was: The <=> operator)

2009-03-13 Thread michael
> On Friday 13 March 2009 09:48:36 Michael wrote: >> I'm sorry for the rant, but nulls in databases make me see red! NULLS >> ARE GARBAGE! >> >> You are using a 'NULL-safe equal to operator', meaning, WHERE NOT >> group_id = 3, and oh, by the way, I DON'T WANT ANY NULLS TO QUALIFY AS >> 3. >> >>

avoiding use of Nulls (was: The <=> operator)

2009-03-13 Thread Ray
On Friday 13 March 2009 09:48:36 Michael wrote: > I'm sorry for the rant, but nulls in databases make me see red! NULLS > ARE GARBAGE! > > You are using a 'NULL-safe equal to operator', meaning, WHERE NOT > group_id = 3, and oh, by the way, I DON'T WANT ANY NULLS TO QUALIFY AS 3. > > And yes this

Using or not using index

2009-03-13 Thread Jerry Schwartz
Running 4.1.22-standard, I have two simple MyISAM tables: Table: temp_del_ids Create Table: CREATE TABLE `temp_del_ids` ( `cust_id` int(11) NOT NULL default '0', PRIMARY KEY (`cust_id`) ) ENGINE=MyISAM DEFAULT CHARSET=utf8 and Table: cust_campaigns Create Table: CREATE TABLE `

Re: The <=> operator

2009-03-13 Thread Michael
I'm sorry for the rant, but nulls in databases make me see red! NULLS ARE GARBAGE! You are using a 'NULL-safe equal to operator', meaning, WHERE NOT group_id = 3, and oh, by the way, I DON'T WANT ANY NULLS TO QUALIFY AS 3. And yes this will be much slower, because now we can't use the index

The <=> operator

2009-03-13 Thread Morten
Hi, I have a query where I want to retrieve all the people who are not in a specific group. Like so: SELECT id, name FROM people WHERE group_id != 3; Since people may not be in a group at all, I also need to test if the column is NULL: SELECT id, name FROM people WHERE group_id

question on loading data and generating uniq table

2009-03-13 Thread Bernd Jagla
Hi, I wanted to ask some more experienced mysql users to give me some advice on a project I am currently planning. I have a text file with three columns: strName(char6), position(integer), str(char36) This file has some 3 billion rows (3,000,000,000). There are some "str"s that are duplicate