[Python-ideas] Application awareness of memory storage classes

[Nick Coghlan]

On 24 May 2016 at 23:26, Nick Coghlan <ncoghlan at gmail.com> wrote:
> I'm not talking about using SQL Alchemy itself for this (as you say,
> the implementation details of the underlying persistence model are all
> wrong), I'm talking about studying the way SQL Alchemy session
> specifically, and the way it manages the in-memory state while a
> transaction is open, and then flushes that state to the database when
> the transaction is completed. It's a thought prompted by a
> presentation Mike gave at PyCon US 2013:
> https://speakerdeck.com/pyconslides/sqlalchemy-session-in-depth-by-mike-bayer
>
> Now, David might investigate that, and decide it's more complexity
> than is needed given persistent RAM, but it's the nearest
> already-in-existence thing I know to what I believe he's aiming to
> build, and it also handles the distinction between persistent state
> (database row for SQL Alchemy, memory allocated in NVRAM for this) and
> ephemeral state (elements dynamically allocated in normal RAM for
> both).

Hah, now there's an interesting idea: you actually *could* use SQL
Alchemy itself with an sqlite in-memory database, but ensure the
latter was allocated in NVRAM :)

Cheers,
Nick.

-- 
Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia