Sqlite-net: [BREAKING CHANGE] SQLiteConnectionString ctor
A third required argument (object key) was added between versions 1.4.118 and 1.5.231 to SQLiteConnectionString ctor so this breaks libraries which tried to use it.
Btw. I mention that in all other ctors (SQLiteConnection, SQLiteAsyncConnection) it is added as optional (object key = null).
plamen-i
All 6 comments
Ah, it was this commit, which changes the ctors. But why is the SQLiteConnectionString the only, where key not defaults to null?
charlenni
on 11 Dec 2018
Yes, this was a mistake. Sorry for the trouble. I'll work on it this week.
praeclarum
on 13 Dec 2018
@praeclarum Do you already know the date, when this bugfix will be released?
RSBlek
on 17 Dec 2018
I have a fix in place and will release a beta today. If it looks good, I'll do a full release.
praeclarum
on 24 Jan 2019
I can confirm that it's back in 1.6:
https://www.fuget.org/packages/sqlite-net-pcl/1.6.249-beta/lib/netstandard1.1/diff/1.4.118/
praeclarum
on 24 Jan 2019
@praeclarum Any idea when 1.6 will be released? Currently users of my library experience a runtime error when upgrading the packages to the latest version, which is something do most of the time.
pauldendulk
on 11 Mar 2019
Related issues
pha3z
路
4Comments
acaliaro
路
6Comments
rneeft
路
6Comments
ToddThomson
路
3Comments
danielPollackGitHub
路
5Comments
Most helpful comment
@praeclarum Any idea when 1.6 will be released? Currently users of my library experience a runtime error when upgrading the packages to the latest version, which is something do most of the time.