Viewing 15 posts - 5,671 through 5,685 (of 6,041 total)
An MP3 player and an automobile engine are two unrelated systems that should not be tightly coupled.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 23, 2011 at 5:14 pm
Ian Scarlett (3/23/2011)
Peugeot in Europe were found to...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 23, 2011 at 8:09 am
nelsonj-902869 (3/23/2011)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 23, 2011 at 8:05 am
It's crazy to think that the audio system in some cars can be wired to the ignition system in such a way that that a hacked MP3 file could kill...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 23, 2011 at 6:32 am
DataChomp (3/22/2011)
Naturally, my favorite data product is SQL...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 22, 2011 at 8:19 am
If you call a SQL DBMS "relational" then what do you expect me to call a DBMS that really is relational? How can we have a proper discussion about different...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 21, 2011 at 2:49 pm
So you are acknowledging that those problems exist in SQL. In fact you go to a lot of trouble to avoid them. Sometimes there are no workarounds and sometimes the...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 21, 2011 at 12:14 pm
David Portas (3/21/2011)
Eric M Russell (3/21/2011)
Aging and inadequate are not descriptive enough terms; could you elaborate more on what you perceive as the "fundamental problems of SQL"?
The problems of SQL...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 21, 2011 at 9:48 am
David Portas (3/20/2011)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 21, 2011 at 8:21 am
richardd (3/18/2011)
Eric M Russell (3/17/2011)
If an application must use VarDate columns, then they should at least code it using ISO standard format YYYYMMDD...
But if you're using real dates, why not...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 18, 2011 at 1:16 pm
CirquedeSQLeil (3/17/2011)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 17, 2011 at 2:46 pm
Ron Porter (3/17/2011)
Mike B in AK (3/17/2011)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 17, 2011 at 11:23 am
richardd (3/17/2011)
Nakul Vachhrajani (3/16/2011)
I have seen people using VARCHAR for storing everything (dates, money, floats)! Their excuse? Globalization/Internationalization.
How can anyone claim that storing a date as the string "09/01/2001" is...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 17, 2011 at 10:04 am
The representation of dates as character strings in a database (what I'll call a "VarDate") is one of the leading causes of business intelligence disasters.
The day will come when another...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 17, 2011 at 7:41 am
There are many different scenarios, but if what you need is access to the database itself, then you can always attach a copy of the mdf file(s) to a SQL...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
March 16, 2011 at 7:44 am
Viewing 15 posts - 5,671 through 5,685 (of 6,041 total)