Hi Cloud,
this often occurs when the path to the database includes a non-ascii
character.
In my dev environment, the path to the database deliberately contains an
umlaut and the original code base of hdbc.sqlite3 from John Goerzen,
version 2.0 version 2.1 thus does not work.
John
Günther Schmidt wrote:
Hi Cloud,
this often occurs when the path to the database includes a non-ascii
character.
In my dev environment, the path to the database deliberately contains an
umlaut and the original code base of hdbc.sqlite3 from John Goerzen,
version 2.0 version 2.1 thus
John Goerzen wrote:
I do recall some discussion about data within a database; I don't recall
one about the filename of it, which would certainly be a separate
discussion. I can see why a connectRaw or some such function could be
I have just pushed a patch to my git repo that adds
Hi John,
let me first of all apologize, I didn't mean to criticize you, I'm sure
you had good reasons for those changes, I'm merely mean to state how
they did affect me after switching to HDBC 2.1.
Since after the rollback they no longer occurred I surmise that there is
a connection.
The
Günther Schmidt wrote:
Hi John,
let me first of all apologize, I didn't mean to criticize you, I'm sure
you had good reasons for those changes, I'm merely mean to state how
they did affect me after switching to HDBC 2.1.
No, I completely understand and I'm not offended; but I didn't want
