I can't prevent it being output as a consumer of the Go library. I've needed to invest effort into my build chain to filter the warning; so there's been some amount of pointless labor as a consequence. It might be possible for the go-sqlite3 author to update the build commands to suppress it?
All that said, certainly, I can live with the extra output in most of my builds. That said, it's harmless until the deprecation turns into a removal at the OS level, at which point ignoring the error becomes a sudden incompatibility with SQLite bindings. On Tue, Oct 4, 2016 at 12:59 PM Richard Hipp <d...@sqlite.org> wrote: > On 10/4/16, Judson Lester <nya...@gmail.com> wrote: > > > > Would you be so kind as to let me know when/if there's a SQLite ticket > for > > this so that I can link it back to the project I encountered this in? > > It's a harmless warning. *Harmless*. Can you not simply ignore it? > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
