Using jdbc driver in eclipse

To do that: - Go into the properties of your project - Select 'Java Build Path' in the left hand column - Select the 'Libraries' tab in the centre part of the window - Click the Add JARs button - this will give you a list of your projects in eclipse - expand your project and into the lib folder - your jar will be there.

Select the option of Add External Jar from the Build path and then browse to the location where the Jar is downloaded, select it and add it. If you are not able to find the Jar while browsing through build path, check the location in windows explorer and confirm that it is where you are searching for it. You asked how to "set up jdbc in eclipse". Here is my take on your question. If this isn't the answer to your question maybe it will help someone else.

Click Add You will be able to test the connection at this point. Eclipse makes it obvious how! Click the Test connection button. As far as JPA-enabling your application, there may be a way to have eclipse set that up ie right click on your project and maybe there is something in the context menu. It would set up a persistence. I don't know off the top of my head. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow.

Learn more. Ask Question. Asked 9 years, 7 months ago. Active 2 years, 1 month ago. Viewed k times. Improve this question. If you choose to create and maintain your database here using MySQL or third-party tools, you can skip this activity.

Please don't be confused by what I've said here. I'm not really making use of DTP in this tutorial. I'm just telling you that it exists and it's potentially useful. This can be an open-ended problem; myriad possibilities exist, but I'll try to corral the important points for you here.

Filter on "mysql". Other Linux platforms support differing advantages for installing software and often come with MySQL already set up. Starting the service, setting the password, etc. Where more than one possibility is presented to you, choose the. To understand how setting up the JDBC connector fits into the bigger picture of libraries, please peruse Using different libraries in development.

Otherwise, come back to follow these instructions after you've set up your first project. The procedure outlined here will help you set this up the first time for your Eclipse workspace.

If it's already set up, the steps are even more obvious. For the next project in the same workspace, you will be able to abbreviate this process because it will already be set up, but you don't have to use it: you can create another one, use a different database vendor, etc. When you've moved the workspace from one computer to another or something else happens to invalidate the workspace assumptions, that is, the various Build Path settings are broken because the User Libraries, including and especially for this discussion the Connectivity Driver Definition , you must rebuild all of this.

This process is more complicated than for a "simple" User Library. To remove a driver definition so that you can re-add it from scratch to match its actual location on disk:. Note: the following statement loads the driver class, creates an instance of it, and registers the driver. Now run the project by right-clicking on DvdJdbc. You should get something like the following error output in your console window:.

The error results from the fact that, after installing MySQL, we didn't in fact create a database table or give it some values and here we are trying to run against no database at all. Let's create a database and populate it.

This can be done one of several ways. These are all options on both Windows and Linux. In this tutorial, we'll give a very quick nod to doing this from Java. Then, we'll cover doing it using tools that came with MySQL.

Covering Eclipse Data Tools Platform is an interesting discussion, but best left for another tutorial. A bit out of order, some of the code in this tutorial expects that you've created a new database in MySQL named dvdcatalog.

If you don't do this up front, some of the examples may fail. Eventually, you are shown how to do this by hand. The following example shows how to get in trouble here: in order to connect to the database, you supply a URL that contains an expectation that dvdcatalog exists, that there is a user root , and that its password is test Missing any of this, you'll fail and, if new at this, you might not immediately realize why.

You should create a database and table s by hand using the command-line interface or, perhaps, a GUI administrator utility. This is because it would be fairly unusual to do it any other way, though you could. To do this programmatically, from Java, you must have a connection to an already existing database table. The code for doing this is here. Arguably, the simplest way to set up a trivial database and one or more tables is to use the command-line environment that comes with MySQL.

Also, it works identically between Windows and Linux. Then I type help. Mostly, we'll just use SQL statements to create a table with schema. SQL is not case sensitive, so you may use case to indicate keywords or just ignore it altogether. I use upper case for keywords in my coded SQL statements, but I don't use it when I'm typing at the command line. You'll just recreate it the way you want it. If you want, you can create it in a file, create-dvd.

The advantage to keeping important statements of schema in SQL scripts like this is that a it's easier to correct and resubmit the statement and b it provides a minor level of back-up for re-creating the database. Run the project again Now that you've done this much, try running the application again by right-clicking on DvdJdbc.

You'll get a different error in the Eclipse console window. All these false starts are only to get you used to what errors look like and what they mean. You can look up details on MySQL vendor error simply by searching for the error number on the web: "mysql error "—in this case, what's reported is enough.

The reason this doesn't work is because a closer look confirms that DvdJdbc was originally written as a command-line utility to use to populate the database and the data to write to the table was supposed to have been passed on the command line. Here we're trying to insert a new row in our recently created table using createStatement and executeUpdate :.

The problem is that we don't actually have any values to insert since we're not gathering them yet. Our test code assumes we're using this class from a command line where we'll supply the data. At this point, we'll abandon the DvdJdbc class in the rest of the tutorial. To get on with our examples on actual data in the database, we'll insert two rows of use in our exercise on reading data.

This is because we have as yet put no data rows into the table. Let's go back and put two in. We're using a numeric rating system for US ratings and keeping the film rating just as a number:. Because I had only put one title in before I quit writing for the day, I had to add the second the next day. To futher illustrate using the command-line utility, here's what I did:. Now let's list our two DVD titles. Under the same package, create a new Java source file, DvdList.

Now run the new Java source in the project by right-clicking on DvdList. Now that we've got the two titles and read them back, let's look at some more command-line examples of things to do. These are statements you can code in Java, as part of a larger, more useful program. With two sample entries entered into our table by hand, we could use Java to do that instead. However, let's learn how to make a change to one of them and, at the same time, learn how to use a prepared statement—which would be very useful in creating rows too.

Here's the code. What we've done is to replace the Statement of DvdJdbc with PreparedStatement , then use question marks as variables in place of hard title names. Then, we perform variable replacement using some methods inside this class. We also jettison the use of command-line arguments for gathering data for the rows. Instead of running this example as we have others like DvdList. We first need to set a breakpoint so that we can stop in the debugger. Set a breakpoint in your code on line 28 below assuming it's the same line number in your code: change it if it's not.

You do this by double-clicking in the column to the left of the one in which you see the line numbers. Yup, there sure is. Well, actually, a DataSource is just an interface, so we need to create an object that implements that interface.

We can tell it that by using the setUrl method:. So, we need to create a Connection object. We can do that with:. OK, I used a bit more code. Because setting up a DataSource might throw an exception, I want to wrap that in a try-catch block. Note, though, that a Connection implements the AutoCloseable interface, so I can use the try-with-resources statement to make my code a little cleaner.

A plea: this exception-catching code is horrendous. When you run this program, a file named test. The code is simpler, but Oracle recommends using a DataSource for creating connections.

Creating a table is a nice example, because you will use the same concepts to perform many other database operations, other than reading from the database. Anyways, you start by creating a DataSource object and a Connection object. To create the Statement object from a Connection object named conn, do the following:.

Again, a Statement implements AutoCloseable, so you can use a try-with-resources statement to simplify your code see the full example code below. To run the command, pass it into executeUpdate as a String. I could just pass a String constant in, but I thought my code was a little more readable this way. Note: rv is short for return value. When you run it, it creates the table.

Note that rv will have the value 0, because no rows were updated. Inserting rows into the table is basically the exact same code, you just change the query String:. When you call executeUpdate , it will return the value 1, because you have updated 1 row. In my example, you can see they are both wrapped inside the same try-with-resources statement:. Once again, when updating and deleting rows, you use the same code, just change the query string.