blob: 0724c38afa0acf9a768f8d32d4b61377ad19d962 (
plain)
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
|
<?xml version="1.0"?>
<document>
<properties>
<author email="jahlborn@users.sf.net">James Ahlborn</author>
<title>Upgrading from Jackcess 2.x to 3.x</title>
</properties>
<body>
<section name="Jackcess 3.5">
<subsection name="So what changed, now?">
<p>
Jackcess 3.5 is binary compatible with previous 3.x versions.
However, a few default settings have changed which will change the
behavior of Jackcess out of the box. The old behavior is still
available, but you must now configure it explicitly.
<ul>
<li><b>DateTypeType default has been changed to
LOCAL_DATE_TIME.</b></li>
<ul>
<li>The Jackcess API was originally built using the Date type
for representing date/time values. However, Access databases
are inherently "local" time (they contain no timezone info).
The LocalDateTime type in jdk8+ is a more accurate value for
relaying Access date/time values. As of the 3.0 release, the
Jackcess API supported using <i>either</i> date/time type,
depending on the configured DateTimeType for the Database.
However, in order to maintain backwards compatibility, the
default was kept as DATE. As of the 3.5 release, the default is
now LOCAL_DATE_TIME. The legacy behavior is still available,
and can be enabled by configuring the DateTimeType appropriately
(either per Database or via system property).</li>
</ul>
<li><b>Expression evaluation is enabled by default.</b></li>
<ul>
<li>Optional expression evaluation was added back in the 2.2
release, but left disabled as the implementation matured. The
support is mature enough now to enable this behavior by default.
Expression evaluation can still be disabled by configuring the
Database appropriately (either per Database or via system
property).</li>
</ul>
</ul>
</p>
<h4>Working with Jackcess Encrypt</h4>
<p>
If you are using the <a href="https://jackcessencrypt.sourceforge.io/">Jackcess Encrypt</a> project, then you will need to
use a version compatible with the relevant Jackess API.
The version 3.5 release maintains compatibility with the Jackcess
Encrypt 3.x releases.
</p>
</subsection>
</section>
</body>
</document>
|
