Not support Unicode name

[cxocto2099]

my database name is "数据库.db" , because it's created and used by another software , I cann't change it to an English name.

Then I found when used : ws4sqlite --db 数据库.db
It showed:
ws4sqlite v0.16.5, based on sqlite v3.50.3

• Serving database '数据库' from 数据库.db?_pragma=journal_mode(WAL)
  • No valid config file specified, using defaults
  • Using WAL
• Web Service listening on 0.0.0.0:12321

But I cann't posted data on http://localhost:12321/数据库
reply:
{
"reqIdx": -1,
"error": "Cannot POST /%E6%95%B0%E6%8D%AE%E5%BA%93"
}

hope to fix it. Thank you.

[proofrock]

Well received. I'll try to reproduce. Can you try using curl, and share the commandline?

[proofrock]

Proposed fix in commit a5eea65

Prep

CD to project's dir. I tested under Linux/amd64.

make build
mkdir -p ws4sqlite_unicode_test
cd ws4sqlite_unicode_test
sqlite3 "数据库.db" "CREATE TABLE test (id INTEGER PRIMARY KEY, name TEXT); INSERT INTO test (name) VALUES ('test data');"
../bin/ws4sqlite --db 数据库.db

Test

curl -X POST http://localhost:12321/数据库 -H "Content-Type: application/json" -d '{"transaction": [{"query": "SELECT * FROM test"}]}'

Before fix

{"reqIdx":-1,"error":"Cannot POST /%E6%95%B0%E6%8D%AE%E5%BA%93"}

After fix

{"results":[{"success":true,"resultHeaders":["id","name"],"resultSet":[{"id":1,"name":"test data"}]}]}

@cxocto2099 can you build the new version (current main branch) and see if it solves for you? If not, tell me your SO/arch and I'll provide a binary.

I added the TestUnicodeDatabaseName test case to ws4sqlite_test.go.

[cxocto2099]

Thank you so much to fix it . But I had found your another project https://github.com/proofrock/sqliterg can work. So I try to use that .
My system is windows, and I don't know how to build it, thank you to provide the binary.

[proofrock]

https://github.com/proofrock/ws4sqlite/releases/tag/v0.16.6pre

Use this. sqliterg is unsupported, it was an experiment.

[cxocto2099]

Thank you so much, it works now ! 👍
But here is another issue , or maybe not :
I use an old windows software which programed by VB6 with LiteX sqlite3.dll to open this sqlite datebase , and it work normally.
But when I use ws4sqlite or sqliterg to open this database, just open, not insert any data by the network , and my database will be modified , and my old software can not open it anymore , show "file is encryted or is not a databse".
Then I compare the new database and old one ,then find :

It seems that it will auto change the 18th and 19th byte from 01 to 02 , then my old software can not recognized it anymore.
And I check that they mean Write Version and Read Version .
I try to use other db software like "DB Browser for SQLite" to open and change data in my old database , this 2 bytes still 01.
Then I changed the db drivers to ODBC , and my software work again.
So maybe it is a issue , or not .

[proofrock]

Good, I'll release an "official" release now.

About your other question, it never happened to me. The following is what Claude says on the matter, take it with a grain of salt but maybe it's useful:

---

This is a known compatibility issue with SQLite's database format versioning. Here's what's happening:

The Problem:

• Byte 18 (Write Version) and Byte 19 (Read Version) in the SQLite header control format compatibility
• 01 01 = Legacy format (SQLite < 3.3.0, ~2006)
• 01 02 = Write-Ahead Logging (WAL) compatible format
• 02 02 = Full WAL mode

Your VB6 app with LiteX sqlite3.dll uses an ancient SQLite version that only understands format 01.

Why ws4sqlite/sqliterg change it:

Modern SQLite libraries automatically upgrade the database format to 02 (WAL-compatible) when opened, even without enabling WAL. This is standard behavior since SQLite 3.7.0 (2010).

Solutions:

Option 1 - Downgrade format after opening:

# After using ws4sqlite, manually reset the bytes
printf '\x01\x01' | dd of=database.db bs=1 seek=18 count=2 conv=notrunc

Option 2 - Force legacy format in modern tools:

-- Before any operations
PRAGMA legacy_file_format = ON;
VACUUM;

Option 3 - Update your VB6 app (recommended):

Replace LiteX sqlite3.dll with a modern SQLite DLL that supports format version 2. Download from https://www.sqlite.org/download.html

Option 4 - Use compatibility wrapper:

Create a script that:

1. Opens DB with modern tools
2. Runs PRAGMA legacy_file_format=1; VACUUM; after changes
3. Resets bytes 18-19 to 01 01

Why DB Browser doesn't trigger this:

DB Browser likely has legacy format detection and preserves the original format version unless you explicitly enable WAL or modify certain pragmas.

Your ODBC solution works because:

ODBC drivers often include compatibility layers that handle format conversion transparently.

Is this a bug?

No - it's intentional SQLite behavior. Modern versions upgrade the format for better performance/features. Your legacy VB6 app needs updating or you need format conversion middleware.

Recommended fix:

Update the SQLite DLL in your VB6 application. It's a drop-in replacement and will solve this permanently.