Re: [sqlite] Exposing compile-time limits?

2017-02-06 Thread Richard Newman
> > We do strive to contain unnecessary growth in the number of > interfaces. Remember that we are promising to support every interface > until 2050. That argues for keeping the number of APIs to a minimum. > Sounds good to me. Thanks for clarifying!

Re: [sqlite] Exposing compile-time limits?

2017-02-06 Thread Richard Hipp
On 2/5/17, Richard Newman wrote: > Hello folks, > > `sqlite3_limit` allows callers to discover the run-time value of limits > such as `SQLITE_LIMIT_VARIABLE_NUMBER`. > > Callers can also *set* each limit, so long as the value is smaller than a > compile-time define, in this

Re: [sqlite] Exposing compile-time limits?

2017-02-06 Thread Clemens Ladisch
Richard Newman wrote: > `sqlite3_limit` allows callers to discover the run-time value of limits > such as `SQLITE_LIMIT_VARIABLE_NUMBER`. > > Callers can also *set* each limit, so long as the value is smaller than a > compile-time define, in this case `SQLITE_MAX_VARIABLE_NUMBER`. > > But callers

[sqlite] Exposing compile-time limits?

2017-02-06 Thread Richard Newman
Hello folks, `sqlite3_limit` allows callers to discover the run-time value of limits such as `SQLITE_LIMIT_VARIABLE_NUMBER`. Callers can also *set* each limit, so long as the value is smaller than a compile-time define, in this case `SQLITE_MAX_VARIABLE_NUMBER`. But callers have no good way of