We had a lot of discussions when I was on the committee (years ago)
about specific data types, such as dates. The IBM guy pushed very hard
for storage to be generic. Part of it was also political. We did not
want to trample on the language side of things. Dates were just one of
these. And that remi
On 1/9/2014 1:49 PM, John Abreau wrote:
My biggest issue with SQL is the lack of standardization for date
arithmetic. I've found over the years that date arithmetic was essential to
almost all the applications I wrote that used a database back-end, and this
was the one sticking point that prevent
John Abreau writes:
> My biggest issue with SQL is the lack of standardization for date
> arithmetic. I've found over the years that date arithmetic was essential to
> almost all the applications I wrote that used a database back-end, and this
> was the one sticking point that prevented me from c
My biggest issue with SQL is the lack of standardization for date
arithmetic. I've found over the years that date arithmetic was essential to
almost all the applications I wrote that used a database back-end, and this
was the one sticking point that prevented me from completely abstracting
the data
On January 8, 2014 at 2:21 PM Eric Chadbourne wrote:
...
> I haven't played with the NoSQL stuff yet. Probably because I find
> sql and it's super sets to be quite useful. One of you posted this a
> while back. Still cracks me up.
>
> http://www.youtube.com/watch?v=b2F-DItXtZs
SELECT "opini
First, databases are a mature technology. While there are always new
things an features. it all comes down to wanting to store lots of data
securely, and be able to retrieve that data quickly and logically. I
once sat on the ANSI standards database committee, and I fully
understand some of the thin
Bear 1: "I need Agile. I need the one with big charts."
Bear 2: "Oh God, I think I just had an aneurysm."
Ahahahha! That was great. I honestly don't know a lot about
development methodologies. I just like to make stuff. So no strong
opinion. Funny!
On Wed, Jan 8, 2014 at 3:10 PM, Bill
Choosing the FOTM-1337 tool is rarely a good idea.
--
Rich P.
___
Discuss mailing list
Discuss@blu.org
http://lists.blu.org/mailman/listinfo/discuss
Are public roads and highways dead, with regard to feature development? Perhaps
"dead" is not the best word choice. A more accurate word might be "mature".
It's not a bad thing for a technology to be mature. Once it reaches that stage,
it can be treated as infrastructure, and new things can be
On 1/8/2014 2:21 PM, Eric Chadbourne wrote:
I lurk one of the postgresql dev lists and they are constantly making
new commits and there always seem to be new features being added, most
of which I haven't even started playing with. But I think I hear what
you're saying. It's an older technology
I lurk one of the postgresql dev lists and they are constantly making
new commits and there always seem to be new features being added, most
of which I haven't even started playing with. But I think I hear what
you're saying. It's an older technology that's been pretty well
explored and polished.
'm not saying they are "dead" as in no one is using them, I'm more
thinking they are dead with regard to feature development.
PostgreSQL and MySQL and the commercial databases just seem less
"important" these days with things like MongoDB and Cassandra. Don't get
me wrong, I think the NoSQL crowd
12 matches
Mail list logo
