Thank you for the clarification. On Wed, Oct 31, 2018 at 6:03 PM Richard Hipp <[email protected]> wrote:
> On 10/31/18, Roman Ivasyshyn <[email protected]> wrote: > > > > I faced with an issue of creating int array with the same name without > > closing connection. > > That is not allowed. But you can use sqlite3_intarray_bind() to > change the array to which the intarray table is bound, or the length > of the array. > > Another option is to use the carray() table-valued-function instead of > the intarray virtual table. The carray() function requires you to > bind the array, the array length, and the array datatype at run-time. > Multiple instances of the carray() table valued function, each with > different array bindings, can participate in the same join. You do > not need to create multiple instances of carray(), one for each array. > Indeed, that is not even allowed. Instead in the single carray() > table valued function can be reused for each array. > > More information on carray here: https://www.sqlite.org/carray.html > > The intarray virtual table predates the ability to have table valued > functions in SQLite. Intarray continues to be used for testing > purposes but is no longer recommended for production use. I have > added a warning to this effect in the header comment. > -- > D. Richard Hipp > [email protected] > _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
