RE: Re: JDBC/ODBC: Technological choice

2001-06-06 Thread Jann VanOver
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:[EMAIL PROTECTED]] Sent: Thursday, May 24, 2001

RE: JDBC/ODBC: Technological choice

2001-05-31 Thread Twylite
Hi, I recently analyzed a JDBC application for performance problems (using JProbe) and found that 2/3 of my time was being spent by the driver looking up my column number with the name. Always refer to columns by number, and read them all in one time -- first to last -- into a data structure

RE: JDBC/ODBC: Technological choice

2001-05-30 Thread Jann VanOver
: Alexandre Bouchard [mailto:[EMAIL PROTECTED]] Gesendet: Donnerstag, 24. Mai 2001 21:49 An: [EMAIL PROTECTED] Betreff: Re: JDBC/ODBC: Technological choice snip/ That's really bizar... And that sucks. Where does this limitation come from? The driver? Access? Would this alternative syntax: String x

Re: JDBC/ODBC: Technological choice

2001-05-24 Thread aswath satrasala
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

Re: JDBC/ODBC: Technological choice

2001-05-24 Thread Guido Medina
not try to reinvent the wheel my friend !!!, that's all... Regards... Guido. P.D: I also hate ASP :-) - Original Message - From: aswath satrasala [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 24, 2001 1:33 PM Subject: Re: JDBC/ODBC: Technological choice Hi, First, I would

Re: JDBC/ODBC: Technological choice

2001-05-24 Thread Alexandre Bouchard
Yeah, that is true, for example, with one odbc pointing to and mdb for example you cannot do this: rs.getString(1) and after try to do it again, you must do TYPE x = rs.getTYPE(n); and read x the times you want but no read a column more than once from Query... That's really bizar... And

Re: JDBC/ODBC: Technological choice

2001-05-24 Thread Guido Medina
Well, I guess this is a bug in mdb, is better to work with variables and forget about bugs...that's all...Guido - Original Message - From: Alexandre Bouchard [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 24, 2001 3:49 PM Subject: Re: JDBC/ODBC: Technological choice Yeah

RE: JDBC/ODBC: Technological choice

2001-05-23 Thread Brian George
Please UNSUBSCRIBE me. I did not subscribe to this listserve. -Original Message- From: Alexandre Bouchard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 23, 2001 5:34 PM To: tomcat-user Subject: JDBC/ODBC: Technological choice Hello guys I am building an intranet on a

RE: JDBC/ODBC: Technological choice

2001-05-23 Thread William Kaufman
-first, is it possible to use a JDBC IV sheme with Tomcat Yes. -if so, how is it possible? How is it made? The same way you use any JDBC implementation. In other words, where can i find documentation about that? The obvious place would be Sun's JDBC home page: