Nah, SQL knowledge will always be required.  The crud stuff is fine for
simple (I can't be arsed typing SQL) processes but fails way short in the
more complex procedures.

There will never be a time where not knowing SQL will be in existence, well
certainly not in our coding lifetime.

SQL is here to stay, let's use it, but use CRUD stuff when you want quick
and effective code re-use but do not think ever that it will replace T-SQL
programming, it won't.









"This e-mail is from Reed Exhibitions (Oriel House, 26 The Quadrant,
Richmond, Surrey, TW9 1DL, United Kingdom), a division of Reed Business,
Registered in England, Number 678540.  It contains information which is
confidential and may also be privileged.  It is for the exclusive use of the
intended recipient(s).  If you are not the intended recipient(s) please note
that any form of distribution, copying or use of this communication or the
information in it is strictly prohibited and may be unlawful.  If you have
received this communication in error please return it to the sender or call
our switchboard on +44 (0) 20 89107910.  The opinions expressed within this
communication are not necessarily those expressed by Reed Exhibitions." 
Visit our website at http://www.reedexpo.com

-----Original Message-----
From: Denny Valliant
To: CF-Talk
Sent: Sun Aug 27 09:45:42 2006
Subject: Re: Top 100 ColdFusion Programmers

On 8/27/06, Robertson-Ravo, Neil (RX) <[EMAIL PROTECTED]>
wrote:
>
> Knowing SQL is a v.important part of the whole package. No excuse for not
> knowing a decent about of T-SQL.


LOL.

I've got a freakishly long, and irreparably inconcise draft response to
Aaron, but
I think I'll just create a blog, and post it there, if that's not a faux
pas.  It's long.
And semi "stream of consciousness"-ish.  Probably pretty weak, really.

Basically I say how reactor (still pre-beta) has Object Oriented Queries,
that
are pure Reactor, and thus port-able to various DBs, by definition.  More
than
just simple CRUD stuff!

And I said I don't think it's quite right how interwoven SQL & languages are
in general. I know I'd love it if there was an ORM/API that would use all
the
cool features of the various databases, Native when possible, emulated
where required.  Plus custom, coder-useful stuff ta boot...
Right now you need PL-SQL, T-SQL, not sure what postgress [P]SQL is
called (I usually pronounce postgree(?) wrong ;), along with mysql
(not sure what it's called off hand either, heh. MSQL?)...

I mean, sheesh.  Forget about just swapping DSNs the instant you use one!
(you better know the equivalent in the new dialect!  'cept fer ANSI, in
general,
of course ;)

Trouble is, stuff like this is intensive!  And the ORMs themselves aren't
easily switchable(generally)- reading the wikipedia entries was interesting.

Plus, each DB is geared for what it's geared for. Guess that matters, neh?
.....

T-SQL... pshaw. PL's where the $$'s @!
(& did I mention that wikipedia ROCKS?)

Yeah, I'd say right now you pretty much have to knoqw SQL... but I foresee
change...  more general, and more specific; at the same time.

As usual. [=
:denny




~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four 
times a year.
http://www.fusionauthority.com/quarterly

Archive: 
http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251178
Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm
Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4

Reply via email to