We use ball-bearings. Everybody's using ball-bearings now-a-days.
Hey! It's all ball bearings nowadays. Now you prepare that Fetzer valve with some 3-in-1 oil and some gauze pads, and I'm gonna need 'bout ten quarts of anti-freeze, preferably Prestone. No, no make that Quaker State.
It is simply not true that gender-selectable psychological differences are based on environmental conditioning.
There are structural differences in male and female brains. These differences begin during fetal development, and they are triggered by sex-based hormonal conditions.
Would you like to share your traversal with us? All you provided is inserts.
A binary tree is useful for efficiently handling lists of stuff, but RDBMSs already handle the effecient storage of lists, so this example really doesn't suffice.
Here is an excersize for you: create a table of employees with a reports_to_employee_id column. Then provide a SQL statement that will return everone who reports to a chosen employee, and everyone who reports to them, etc. It's easy to store; not easy to retrieve.
I'd like to add a couple of things to those last two points.
When you say "no support for entity sub/supertypes" it is a specific indictment of SQL not RDBMSs in general. I think this one issue illustrates the weaknesses of SQL for those who aren't familiar with it. SQL cannot be used to implement an arbitrary-depth tree traversal using the scheme advocated by the previous poster. The SQL apologists should really try writing an arbitrary-depth tree traversal in SQL and see it for themselves. It can't be done without mucking around with temporary tables or some other nonsense. I have run into this problem a couple of times. Experienced SQL programmers hardly notice it, because they just learn not to think in terms of tree structures. But the problem is still very real. Relational databases are great at storing trees. SQL is terrible at retrieving them.
The NULL handling is similar. SQL programmers learn how to avoid the problems with NULL (usually by making non-nullable columns), but the specific way in which SQL handles NULLs is very problematic, and it leads to buggy systems.
-----BEGIN PGP SIGNATURE----- Version: PGP 8.0.2 - not licensed for commercial use: www.pgp.com Comment: My public key: http://www.cswnet.com/~jwhitled/2003/PGP/
the holy grail of fire prevention: a system that will save both your NOC and the geeks inside it. Somebody ought to try to come up with that. There's probably a lot of money there.
You mean like FM-200? Yeah, somebody out to try to come up with that. It's ozone friendly, too!
I've found that every time I rewrite a piece of code, it gets better and better. Why would I want to copy the old junk that was written by a dumber me two years ago?
There are two reasons why the driving laws in the USA are so lax:
1. There is almost no public transportation.
2. Zoning laws.
People here have to drive because they have no alternative. Outside of the north-east corridor (such as here in Arkansas) it would be economically impossible to stop people from driving. Everything is simply too far apart. There is also a total lack of provisions for walking/biking/horse riding, unless you like walking in a muddy ditch or on a busy road. That's why people caught driving without a license get a slap on the wrist (maybe).
To me, hiding the contents of my e-mail isn't the main issue with encryption. The biggest benefit of encryption would be spoof-prevention. I wish encryption had been built into the e-mail protocols from the beginning so people who get an e-mail from me can know that it is indeed from me and not some spoofer.
I'm developing an automated system for tracking down enemy combatants and dismembering them in the most horrific manner possible...but I refuse to accept military funding.
No, he's right. The Internet is dead. In fact, I've already dismantled my computer and set it out by the street. The Internet is over. Now, who wants to go get a pizza?
Don't worry. All the martians can see is our night side. So stay in unlit areas at night, and you should be alright.
It's the same reason we can't see all of those hot venusian women.
I never took chemistry.
Thanks for the explaination. (Since I can't do the calculation whether on my duff or not.)
He says that an average gallon of gasoline releases 20 pounds of CO2. I didn't realize gasoline was so heavy. A gallon of water is only 8 lbs.
Hey, it can copy all three Lord of the Rings extended editions in just under an hour!
Stop it, you're making me cry.
Ah, the good old days. AUTOEXEC.BAT, I hardly knew ye.
(sigh)
We use ball-bearings. Everybody's using ball-bearings now-a-days.
Hey! It's all ball bearings nowadays. Now you prepare that Fetzer valve with some 3-in-1 oil and some gauze pads, and I'm gonna need 'bout ten quarts of anti-freeze, preferably Prestone. No, no make that Quaker State.
It is simply not true that gender-selectable psychological differences are based on environmental conditioning.
There are structural differences in male and female brains. These differences begin during fetal development, and they are triggered by sex-based hormonal conditions.
Would you like to share your traversal with us? All you provided is inserts.
A binary tree is useful for efficiently handling lists of stuff, but RDBMSs already handle the effecient storage of lists, so this example really doesn't suffice.
Here is an excersize for you: create a table of employees with a reports_to_employee_id column. Then provide a SQL statement that will return everone who reports to a chosen employee, and everyone who reports to them, etc. It's easy to store; not easy to retrieve.
I'd like to add a couple of things to those last two points.
When you say "no support for entity sub/supertypes" it is a specific indictment of SQL not RDBMSs in general. I think this one issue illustrates the weaknesses of SQL for those who aren't familiar with it. SQL cannot be used to implement an arbitrary-depth tree traversal using the scheme advocated by the previous poster. The SQL apologists should really try writing an arbitrary-depth tree traversal in SQL and see it for themselves. It can't be done without mucking around with temporary tables or some other nonsense. I have run into this problem a couple of times. Experienced SQL programmers hardly notice it, because they just learn not to think in terms of tree structures. But the problem is still very real. Relational databases are great at storing trees. SQL is terrible at retrieving them.
The NULL handling is similar. SQL programmers learn how to avoid the problems with NULL (usually by making non-nullable columns), but the specific way in which SQL handles NULLs is very problematic, and it leads to buggy systems.
No country uses SI units, unless I'm just missing all those international weather reports in kelvins.
the holy grail of fire prevention: a system that will save both your NOC and the geeks inside it. Somebody ought to try to come up with that. There's probably a lot of money there.
You mean like FM-200? Yeah, somebody out to try to come up with that. It's ozone friendly, too!
I've found that every time I rewrite a piece of code, it gets better and better. Why would I want to copy the old junk that was written by a dumber me two years ago?
There are two reasons why the driving laws in the USA are so lax:
1. There is almost no public transportation.
2. Zoning laws.
People here have to drive because they have no alternative. Outside of the north-east corridor (such as here in Arkansas) it would be economically impossible to stop people from driving. Everything is simply too far apart. There is also a total lack of provisions for walking/biking/horse riding, unless you like walking in a muddy ditch or on a busy road. That's why people caught driving without a license get a slap on the wrist (maybe).
I know from experience that a many-to-many household-to-address setup is a BAD IDEA. Do not do this to yourself.
Sometimes it is okay to have duplicate addresses in your table, if it will save you headaches in maintenance, reporting, etc.
What about the theory that the earth was once a wet planet? And the corresponding theory that if it was wet it might have once supported life?
"I'm not a nerd. Nerds are smart!"
As everyone knows, when a girl makes an offensive Web site about you, it just means that she secretly likes you.
Small Claims Court counselling?
(Sorry, I had to ask.)
To me, hiding the contents of my e-mail isn't the main issue with encryption. The biggest benefit of encryption would be spoof-prevention. I wish encryption had been built into the e-mail protocols from the beginning so people who get an e-mail from me can know that it is indeed from me and not some spoofer.
I'm developing an automated system for tracking down enemy combatants and dismembering them in the most horrific manner possible...but I refuse to accept military funding.
No, he's right. The Internet is dead. In fact, I've already dismantled my computer and set it out by the street. The Internet is over. Now, who wants to go get a pizza?
Don't worry. All the martians can see is our night side. So stay in unlit areas at night, and you should be alright.
It's the same reason we can't see all of those hot venusian women.
"The total blame for the Colombia accident rests squarly on the shoulders of Kim Johnson of Springfield, MO." Ever have one of those days?
This gives new meaning to the term "vaporware"!