Hi D. Richard Hipp. Sorry for the late reply. I had some email settings
wrong somewhere, and I didn't realize I had a reply until I remembered this
and checked the archives months later. You had written:
>>
>> Is there something we need to do proactively to ensure that schema update
>> appears imm
Hi Simon. Sorry for the late reply. I had some email settings wrong
somewhere, and I didn't realize I had a reply until I remembered this and
checked the archives months later. You had written:
>Can I ask the maximum number of columns you expect to exist in that table
? I'm working up to trying t
Hi José. Sorry for the late reply. I had some email settings wrong
somewhere, and I didn't realize I had a reply until I remembered this and
checked the archives months later. You had asked:
> Are you using BEGIN and END before and after the schema update?
Yes that's correct. We are doing the sch
To clarify, we add a column on our writer connection, and then "SELECT *
FROM table" on the reader connection does not include the column that was
added.
Ben
On Fri, Aug 16, 2019 at 11:32 AM Ben Asher wrote:
> Hi folks! We're running (sqlite 3.27.2) into an issue where we make a
> schema update
On 8/16/19, Ben Asher wrote:
>
> Is there something we need to do proactively to ensure that schema update
> appears immediately from other threads?
>
When a database connection has a read transaction open, it continues
to see a snapshot of the database as it existed when the read
transaction was
On 16 Aug 2019, at 7:32pm, Ben Asher wrote:
> we make a
> schema update (adding a column to a table) on our writer connection
Can I ask the maximum number of columns you expect to exist in that table ?
I'm working up to trying to convince you to add a row to something instead, but
I want to m
Ben Asher, on Friday, August 16, 2019 02:32 PM, wrote...
>
> Hi folks! We're running (sqlite 3.27.2) into an issue where we make a
> schema update (adding a column to a table) on our writer connection, but
> then the schema update isn't immediately available on the read-only
> connections that we
Hi folks! We're running (sqlite 3.27.2) into an issue where we make a
schema update (adding a column to a table) on our writer connection, but
then the schema update isn't immediately available on the read-only
connections that we use on other threads, which causes a crash in our
application (app e
8 matches
Mail list logo