RE: Re: JDBC/ODBC: Technological choice

[Jann VanOver <Ja...@loudeye.com>]

Even some "JOINS" can be done in Access by using the WHERE clause.

Instead of:  SELECT * from A INNER JOIN B ON A.stuff = B.moreStuff

You say:  SELECT * from A, B WHERE A.stuff = B.moreStuff

-----Original Message-----
From: aswath satrasala [mailto:aswath_jboss@hotmail.com]
Sent: Thursday, May 24, 2001 5:07 PM
To: tomcat-user@jakarta.apache.org
Subject: Re:Re: JDBC/ODBC: Technological choice





>From: Alexandre Bouchard <ro...@mac.com>
>Reply-To: tomcat-user@jakarta.apache.org
>To: <to...@jakarta.apache.org>
>Subject: Re:Re: JDBC/ODBC: Technological choice
>Date: Thu, 24 May 2001 14:46:06 -0400
>
>Mmmmmm... i am not sure that I understand. What did you mean by
>"restrictions Access will place"? I think that all I gonna need in my
>scripts are SELECT and INSERT queries. As long as I can use these two SQL
>instructions, I will be happy.
>

If you are using one table for your "SELECT" statements,
then it is fine.
I faced the problem of joining two tables in "SELECT" statements.  This will

normally be the case.


>And for the deployment, i read in a tutorial that to setup a JDBC-ODBC with
>Access bridge all you have to do is:
>
>1-create an Access db
>2-creat the ODBC source (select the pilot MS Access Driver -in ODBC
>manager-, define the db's name and path, define data source's name and 
>path)
>3-in the JSP page, connect to the db:
>Class.forname("sun.jdbc.JdbcOdbcDriver").newInstance();
>Connection con = DriverManager.getConnection("jdbc:odbc:base_de_donnees);
>
>Is that correct? Is there missing steps? If not, it seems simple enough.
>
>
> > Hi,
> > First, I would like to point the restrictions Access
> > will place in using standard SQL, when you are
> > using JDBC or JDBC-ODBC.
> > You may not have the same flexibility in your SQL as with
> > SQL server or oracle.
> >
> > Assuming you know the limitations, you are better off
> > using ASP, if you are using Access. I am not discouraging
> > you from using JSP.  You can as well persuade to use
> > SQL server and starting working on JSP.
> > Working with JDBC/tomcat/JSP is simple, I don't have
> > any problems in my application.
> >
> > However, considering the deployment question, we
> > are still thing of deployment, as you may have to
> > write scripts to set the datasource (if you are using jdbc-odbc).
> >
> > -Aswath
> >
> >
> >
> >
> >> From: Alexandre Bouchard <ro...@mac.com>
> >> Reply-To: tomcat-user@jakarta.apache.org
> >> To: tomcat-user <to...@jakarta.apache.org>
> >> Subject: JDBC/ODBC: Technological choice
> >> Date: Wed, 23 May 2001 20:34:29 -0400
> >>
> >> Hello guys
> >>
> >> I am building an intranet on a window NT environment. I hate ASP, so I
> >> decided to use JSP as the server-side language. I chose Tomcat to run 
>my
> >> JSP
> >> and I installed it as a IIS plugin.
> >>
> >> Now, I have to connect my JSPs with the databases (they use Access --
> >> ouch! ) I never did that before and I don't know if I should use JDBC I

>or
> >> IV. So my questions are:
> >>
> >> -first, is it possible to use a JDBC IV sheme with Tomcat
> >>
> >> -if so, how is it possible? How is it made? In other words, where can i
> >> find
> >> documentation about that?
> >>
> >> -why it is recommended to use JDBC IV when dealing with intranet?
> >>
> >> -JDBC-ODBC bridge vs JDBC IV: how slower? Which one is simplier to 
>setup?
> >>
> >> -Finally, is it difficult to deal with JDBC, to deploy it?
> >>
> >> A lot of question, isn't it?
> >> I would also apreciate if some of you could share their experience of
> >> building a JDBC/JSP/Tomcat infrastructure.
> >>
> >> Thx !
> >>
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at http://explorer.msn.com
> >
>

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com