Talk:JDBC driver
From Wikipedia, the free encyclopedia
[edit] Merger
No problems with the merger as long as no information from any of the individual driver pages including the images is lost in the merger. We can create the merged page here and review it and redirect the others to here once it looks good. Jay 23:45, 4 May 2006 (UTC)
- I don't think I'm in favor of a merger. The trend over time is for articles to get longer and need to be split. I think we will eventually want to split this article. Merging it and then splitting it seems to be a waste.
- In particular, I strongly urge that JDBC type 1 driver not be merged, as it is redirected from JDBC-ODBC_Bridge. I'd like to see this particular article expanded, not merged back.
- Israel Steinmetz 15:01, 24 August 2006 (UTC)
- I don't think we should merge the individual driver pages. Each page can have a list of driver providers, links to tutorials about using a specific driver type etc. The individual pages will tend to grow larger with time. Hence the existing structure seems to be fine. Roshan Kulkarni Oct 15th 2006
[edit] Type 4, bullet point 1
This bullet point implies that there the following necessary:
- That a 'server' be involved.
- That a network connection must be made.
I disagree - a type 4 JDBC driver does not necessarily have to be reliant on an external, network DB. Am I wrong? 67.23.168.161 02:06, 16 December 2006 (UTC)
[edit] Type-3 terminology
In both the description and diagram under type-3, the middle-tier piece of this driver is referred to as an 'Application Server'. I don't believe this is a correct usage of this term. The middle-tier of a type-3 archetecture is typically concerned with servicing driver connections to datasources and from clients. It's not a full blown application server, it isn't even necessarily Java-based.
I suggest keep using a term-like 'middle-tier', and not use 'application server' for this component. --208.204.155.241 16:15, 18 December 2006 (UTC)
