JDBC

[james.grimes@xxxxxxxxxxx (Grimes, James)]

If you stick to SQL and avoid the convenient offerings of PLSQL and TSQL
etc, avoid using code within your database - stored procedures etc, and use
JDBC prepared statements as much as possible, you should get a lot of
database independance. There will always be a few niggly matters eg
implementing outer joins which are different but you can get around this by
keeping your SQL commands away from the code (such as storing it in the
database itself), and you will be able to configure it to suit a particular
database whenever it is absolutely necessary.

> -----Original Message-----
> From: Matthias Carlsson [mailto:matthias.carlsson@xxxxxxxxxxxxxxxxxx]
> Sent: Monday, January 31, 2000 5:21 PM
> To: Advanced Java Mailing List
> Subject: JDBC
> 
> 
> I've written an application which I preferably would like to connect
> to a SQL database. I've never used either SQL nor JDBC before, but
> that's not really relevant right now. 
> What I'd like to know if it with JDBC is possible to write database-
> independent code, so that the application will work with any type
> of database without having to change the code? 
> 
> Thanks,
> 
> [ Matthias Carlsson ]
> [ Programmer (Java, CGI/Perl, Javascript, HTML) ] [ Web Designer ]
> [ E-Mail: matthias.carlsson@xxxxxxxxxxxxxxxxxxx ] [ UIN: 1430647 ]
> 
> ---
> To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
> To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx
> 

---
To unsubscribe, mail advanced-java-unsubscribe@xxxxxxxxxxxxxxxx
To get help, mail advanced-java-help@xxxxxxxxxxxxxxxx