Add the Connection property charset to support from URL

[rtyuy]

Add the Connection property charset to support setting the encoding from the URL. For example, the encoding of early MDB files was not fixed and depended on the encoding used when they were created. When reading older MDB files and the encoding does not match the system's default encoding, it can cause garbled text issues. Therefore, adding an encoding property makes it convenient to set the encoding, such as jdbc:ucanaccess://d:/test.mdb;CHARSET=gbk.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[spannm]

Hello @rtyuy,

It's a good suggestion to add this property.

I've gone over your pr, looking good but I would like some minor adjustments:

• Overload IJackcessOpenerInterface#open and provide default implementation (keeping original signature as-is for backward compatibility)
• Handle UnsupportedCharsetException gracefully in Charset#forName(String) with a meaningful exception message

My additions here: https://github.com/spannm/ucanaccess/tree/pr-24

Do you think you could add a unit test with a database file that uses an uncommon charset?
The db file should be as small as possible in order not to bloat the repo. Look at any JUnit test that extends UcanaccessBaseFileTest as an example. The test database name is derived from the unit test name e.g. MetaDataParameterizedTest ==> metaDataParameterized.accb.

Cheers
Markus

[rtyuy]

ok， I will put a unit test later

[spannm]

Hi @rtyuy,

I've added the feature with minor modifications.

Still, we should add a unit test. Please upload a small mdb with GBK character encoding (the smaller the better in order not to bloat the repo) to this thread or provide a complete unit test.

cheers
Markus