Re: Relational Databases

<stephen>I just want people to realize that
CF is not the answer for database transparency, it is really good coding
and knowledge of the cross DB capabilities exposed by ODBC that allow for
this
</stephen>

this is a very important point. People should realise that all these
applications are just a front end to a ODBC which is also a front end to a
Relational Database management system.

If you really are going to get into this in other than a trivial way, there
really is no substitute for learning the fundamentals.

For example in ASP, once you get past the basic database implementations,
you really do have to learn how to build SQL statements (or at least use
your DB front end to do this for you).

The original question was from someone who had to implement a site in a
short time frame and need a 'quick and dirty 'method.

One of the virtues of ASP is that it is totaly scalable, and once you get
your feet wet you can manipulate DB's XML, file systems etc.

I don't have enough experience of the other systems to know how scalable
they are, but If you are in this for the long haul then you need to look at
this factor as well!

My own (very limited) experience of Cold Fusion is that it is rather like a
WYSIWYG developer for HTML pages in that it hides much of the details of
implementation from the developer. This may be just what you want.

FTR HWG offers online classes for both Cold fusion and ASP,
(www.hwg.org/classes) which IMO are very good. (<disclaimer>I don't teach
either of them</disclaimer>). HWG will also probably be offering a class on
ASP databases in the fall of this year.

Frank


----- Original Message -----
From: Stephen Johnston <pepe(at)gainsay.com>
To: <hwg-techniques(at)mail.hwg.org>
Sent: Thursday, April 06, 2000 7:20 PM
Subject: Re: Relational Databases


> At 11:12 AM 4/6/2000 , you wrote:
> >One of the beauties with CF is that you can design and prototype with
> >Access and then
> >upsize that to MS SQL, Oracle, Sybase or other database platforms without
> >having to
> >re-code the application.
>
>
> Susan-
>
>          I typically chalk this capability up to the ODBC interface, which
> allows for database transparency.  I am not refuting that CF is a good
> tool, but proper coding in almost any application (using ODBC) will allow
> for this.  In addition certain database capabilities will not be
> transferable if you start to use them.  I just want people to realize that
> CF is not the answer for database transparency, it is really good coding
> and knowledge of the cross DB capabilities exposed by ODBC that allow for
this.
>
> -Stephen Johnston
>
> ================================================
> President
> Gainsay.com, Inc.
> http://www.gainsay.com/
> Database Driven Internet Application Development
>

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA