1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
|
<?xml version="1.0"?>
<document>
<properties>
<author email="jahlborn@users.sf.net">James Ahlborn</author>
<title>Jackcess Cookbook</title>
</properties>
<body>
<section name="Introduction">
<p>
This cookbook will attempt to familiarize the reader with the various
nooks and crannies of the Jackcess API. The API is large due to the
large feature-set that an Access Database provides, so this cookbook
will by no means be exhaustive. However, this will hopefully give the
reader enough useful building blocks such that the rest of the API can
be discovered and utilized as necessary.
</p>
<p>
This cookbook is a cross between a tutorial and a reference, so the
reader should be able to skip to relevant sections without needing to
read the entire preceding text.
</p>
<p>
While this cookbook strives to present best practices for both the
Jackcess API and Java programming in general, at times, the code may
be trimmed for the sake of brevity. For the same reason, pseudo-code
may be used in places where the actual code is not relevant to the
example.
</p>
<macro name="toc">
<param name="section" value="0"/>
<param name="fromDepth" value="0"/>
<param name="toDepth" value="4"/>
</macro>
</section>
<section name="The Basics">
<subsection name="Opening an existing Database">
<p>
So you have an Access Database and you want to do something with it.
You want to use Java, and you may not even be running on Windows (or
you tried the JDBC/ODBC bridge and it failed miserably). Through
some Google-fu, you landed here at the Jackcess project. Now what?
</p>
<p>
Well, the first thing you need to do is open the database. The
entry point class in the Jackcess API is, suprisingly enough, the
<a href="apidocs/com/healthmarketscience/jackcess/Database.html">Database</a> class.
</p>
<source>
Database db = Database.open(new File("mydb.mdb"));
</source>
<p>
That's it, now you have a Database instance (maybe this isn't that
difficult after all).
</p>
<p>
Important note, <i>always</i> make sure you close a Database
instance when you are finished with it (preferably in a finally
block like any other important resource). Failure to close the
Database instance could result in data loss or database corruption.
</p>
</subsection>
<subsection name="Reading a Table">
<p>
Okay, so you have a Database instance, now what? Since pretty much
everything in an Access database lives in a table, grabbing a <a href="apidocs/com/healthmarketscience/jackcess/Table.html">Table</a>
would be the logical next step.
</p>
<source>
Table table = db.getTable("Test");
</source>
<p>
Where's the data? While a <a
href="apidocs/com/healthmarketscience/jackcess/Cursor.html">Cursor</a>
is the best way to interact with the data in a Table, for the sake
of simplicity when just getting started, we will use the simplified
iteration provided by the Table class itself. When reading row
data, it is generally provided as a <code>Map<String,Object></code> where the keys are the column
names and the values are the strongly typed column values.
</p>
<source>
for(Map<String,Object> row : table) {
System.out.prinln("Look ma, a row: " + row);
}
</source>
<p>
So, what's in a row? Well, let's assume your "Test" table is
defined in the following way in Access:
</p>
<blockquote>
<table>
<tr>
<th>Field Name</th><th>Data Type</th>
</tr>
<tr>
<td>ID</td><td>AutoNumber (Long Integer)</td>
</tr>
<tr>
<td>Name</td><td>Text</td>
</tr>
<tr>
<td>Salary</td><td>Currency</td>
</tr>
<tr>
<td>StartDate</td><td>Date/Time</td>
</tr>
</table>
</blockquote>
<p>
Then, given a row of data, we could inspect the various <a href="apidocs/com/healthmarketscience/jackcess/Column.html">Columns</a> and
their values like so:
</p>
<source>
Map<String,Object> row = ...;
for(Column column : table.getColumns()) {
String columnName = column.getName();
Object value = row.get(columnName);
System.out.println("Column " + columnName + "(" + column.getType() + "): "
+ value + " (" + value.getClass() + ")");
}
// Example Output:
//
// Column ID(LONG): 27 (java.lang.Integer)
// Column Name(TEXT): Bob Smith (java.lang.String)
// Column Salary(MONEY): 50000.00 (java.math.BigDecimal)
// Column StartDate(SHORT_DATE_TIME): Mon Jan 05 09:00:00 EDT 2010 (java.util.Date)
</source>
<p>
As you can see in this example (and as previously mentioned), the
row values are <i>strongly typed</i> Java objects. In Jackcess, the
column types are represented by a Java enum named <a href="apidocs/com/healthmarketscience/jackcess/DataType.html">DataType</a>.
The DataType javadoc details the Java types used to return row
values as well as the value types which are acceptable inputs for
new rows (more on this later). One other thing to note in this
example is that the column names in the row Map are <i>case
sensitive</i> strings (although other parts of the API strive to
mimic Access's love of case-insensitivity).
</p>
</subsection>
<subsection name="Adding a Row">
<p>
Awesome, so now we can read what's already there. Of course, lots
of tools can do that. Now we want to write some data.
</p>
<p>
The main hurdle to writing data is figuring out how to get the data
in the right columns. The primary method for adding a row to a
Table is the <a href="apidocs/com/healthmarketscience/jackcess/Table.html#addRow(java.lang.Object...)">addRow(Object...)</a>
method. This method should be called with the appropriate, strongly
typed Java object values <i>in the order of the Columns of the
Table</i>. The order of the Columns on the Table instance <i>may
not be the same as the display order of the columns in Access</i>.
(Re-read those last two sentences again, as it will save you a lot of
grief moving forward).
</p>
<p>
Additionally, when adding rows, we never provide a value for any
"auto" columns. You can provide a value (any value in fact), but it
will be ignored (in the example below, we use a useful constant which
makes the intent clear to any future developer).
</p>
<p>
So, assuming that the order of the Columns on the Table instance is
"ID", "Name", "Salary", and "StartDate", this is how we would add a
row to the "Test" table:
</p>
<source>
String name = "bob";
BigDecimal salary = new BigDecimal("1000.00");
Date startDate = new Date();
table.addRow(Column.AUTO_NUMBER, name, salary, startDate);
</source>
<p>
There you have it, a new row in your Access database.
</p>
</subsection>
</section>
<section name="Starting from Scratch">
<subsection name="Creating a new Database">
<p>
While updating existing content is nice, and necessary, many times
we want to create an entire new Database. While Jackcess doesn't
support everything you may need when creating a new database, it
does support a wide range of functionality, and adds more all the
time. (If you started using Jackcess a while ago, you should
definitely keep tabs on the <a href="changes-report.html">release notes</a>, as your knowledge of what
is possible may be out of date).
</p>
<p>
As of version 1.2.10, Jackcess supports:
</p>
<ul>
<li>Creating databases for Access all versions 2000-2010</li>
<li>Creating columns for all simple data types</li>
<li>Creating tables with single-table Indexes</li>
</ul>
<p>
Some notable gaps:
</p>
<ul>
<li>Cannot currently create tables with (index backed) foreign-key
constraints</li>
<li>Cannot currently create tables with "complex" columns
(attachment, multi-value, versioned memo)</li>
</ul>
<p>
As long as your needs fall into the aforementioned constraints (or
if you can fake it), then let's get started!
</p>
<p>
The first thing we need to choose is the desired <a href="apidocs/com/healthmarketscience/jackcess/Database.FileFormat.html">FileFormat</a>
of the new Database. Armed with that information, we can start
putting the pieces together using the appropriate builder classes.
Notice that the result of creating the new Database is an open
Database instance.
</p>
<source>
File file = new File("test.mdb");
Database db = new DatabaseBuilder(file)
.setFileFormat(Database.FileFormat.V2000)
.open();
</source>
</subsection>
<subsection name="Creating a Table">
<p>
An empty Database isn't very useful, of course, so we probably want
to add a Table or two. The following code will create the table
that we have used in the above examples. Notice that, like Database
creation, the result of the Table creation is an open Table
instance.
</p>
<source>
Table table = new TableBuilder("Test")
.addColumn(new ColumnBuilder("ID", DataType.LONG)
.setAutoNumber(true))
.addColumn(new ColumnBuilder("Name", DataType.TEXT))
.addColumn(new ColumnBuilder("Salary", DataType.MONEY))
.addColumn(new ColumnBuilder("StartDate", DataType.SHORT_DATE_TIME))
.toTable(db);
</source>
</subsection>
<p>
That is a very simple Table. In the real world, we often need Indexes
to speed up lookups and enforce uniqueness constraints. Adding the
following to the previous example will make the "ID" column a primary
key and enable speedier lookups on the "Name" column.
</p>
<source>
// new TableBuilder(...
.addIndex(new IndexBuilder(IndexBuilder.PRIMARY_KEY_NAME)
.addColumns("ID").setPrimaryKey())
.addIndex(new IndexBuilder("NameIndex")
.addColumns("Name"))
// .toTable(...
</source>
<p>
Don't forget to close the Database when you are finished building it
and now you have a fresh, new Database on which to test some more
recipes.
</p>
</section>
</body>
</document>
|
