Discussion
AndySheff said:
He's making a database.
He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
I would expect behaviour to be held in a child table with an effective date as part of the key. Your statement suggests behaviour is a single, rarely changing property of a contact. And why would you select * if you are making a list of contacts? Surely he would select name and address (again, from different tables). And it will make for a very inefficient Christmas Eve if he doesn't perform an order by on the addresses...He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
king Calibri 12. Grrr.
Has to be Galliard. 
wiggy001 said:
AndySheff said:
He's making a database.
He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
I would expect behaviour to be held in a child table with an effective date as part of the key. Your statement suggests behaviour is a single, rarely changing property of a contact. And why would you select * if you are making a list of contacts? Surely he would select name and address (again, from different tables). And it will make for a very inefficient Christmas Eve if he doesn't perform an order by on the addresses...He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
- justsayin
DogLog said:
wiggy001 said:
AndySheff said:
He's making a database.
He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
I would expect behaviour to be held in a child table with an effective date as part of the key. Your statement suggests behaviour is a single, rarely changing property of a contact. And why would you select * if you are making a list of contacts? Surely he would select name and address (again, from different tables). And it will make for a very inefficient Christmas Eve if he doesn't perform an order by on the addresses...He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
- justsayin
Dr Jekyll said:
DogLog said:
wiggy001 said:
AndySheff said:
He's making a database.
He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
I would expect behaviour to be held in a child table with an effective date as part of the key. Your statement suggests behaviour is a single, rarely changing property of a contact. And why would you select * if you are making a list of contacts? Surely he would select name and address (again, from different tables). And it will make for a very inefficient Christmas Eve if he doesn't perform an order by on the addresses...He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
- justsayin
A network admin is drafted into the army and is sent to the firing range for target practice. After firing off a few shots a report comes back that he has failed to get any on target. He looks at the rifle, and then looks at the target. He then puts a finger into the end of the rifle, and with his other hand he squeezes the trigger. His finger is blown off. The admin yells towards the target area, “It’s leaving here just fine. The problem must be at your end.”
LordGrover said:
A network admin is drafted into the army and is sent to the firing range for target practice. After firing off a few shots a report comes back that he has failed to get any on target. He looks at the rifle, and then looks at the target. He then puts a finger into the end of the rifle, and with his other hand he squeezes the trigger. His finger is blown off. The admin yells towards the target area, “It’s leaving here just fine. The problem must be at your end.”
Oh god if I had a penny for every time.......feef said:
Dr Jekyll said:
DogLog said:
wiggy001 said:
AndySheff said:
He's making a database.
He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
I would expect behaviour to be held in a child table with an effective date as part of the key. Your statement suggests behaviour is a single, rarely changing property of a contact. And why would you select * if you are making a list of contacts? Surely he would select name and address (again, from different tables). And it will make for a very inefficient Christmas Eve if he doesn't perform an order by on the addresses...He's sorting it twice.
Select * from contacts where behaviour = 'nice'
SQL CLause is coming to town !
- justsayin
Gassing Station | The Lounge | Top of Page | What's New | My Stuff