Woojong Koh

> @wjkoh: Can you see if this version is better: https://zliide.github.io/camera-web-mobile-orientation/ Yes, your version works perfectly on my phone. Thanks for the fix!

The situation is complex. When a connection is returned to a pool, `resetSession` is called to clear the connection's previous state, ensuring it functions as if it were new. See...

I believe dropping all temporary tables on connection close is a reasonable action. SQLite3 explicitly states that temporary tables are dropped when the connection is closed. This isolation (not being...

Regarding temporary tables, I think it would be acceptable if they were specifically dropped only when a user explicitly calls db.Conn() and then conn.Close(). This depends on whether we can...

Let's return to the original question: how can we use a temporary table for anything useful? In the current situation, a temporary table works similarly to regular tables. Actually, it's...

> Note that temporary tables are not the only aspect of the connection state that could be changed. For example, one could run `PRAGMA busy_timeout=N` - shouldn't that also be...

> First, what you are encountering is just another example of where database/sql's connection pool concept kind of falls flat, because it doesn't give you the ability to convey your...

So, you're saying you would prefer doing things the wrong way, at the cost of doing them the right way? This is a good opportunity to do the right thing....

Has anyone experienced an issue where a temporary table persists after connection closure? I reported this issue as #1330 and am wondering if others have encountered the same problem.

+1. https://firebase.google.com/docs/firestore/vector-search seems very promising to me!