>>>>> "SF" == Stephen Fitch <[EMAIL PROTECTED]> writes:
SF> Hi Mike,
SF> the issue I'm having is I can't find a way to tell the network server
SF> what StorageFactory to use from the network client driver.
SF> On the embedded side of things, I just define a new subsubprotocol
SF> when I start java with:
SF>
-Dderby.subSubProtocol.memory=org.apache.derby.impl.io.MemoryStorageFactory
SF> (alternatively I can change some of the engine code and register it as
SF> a persistent service which results in the same issue)
I am a bit confused about why the use of StorageFactory is decided
when opening a connection. Will it be possible for different
connections to use different StorageFactory within the same system? I
guess different StorageFactory within the same database is not
possible. In that case, why not make it a parameter when creating the
database?
Generally, I would think it would be useful for a single
connection/database be able to use main-memory storage for some tables
and disk storage for others.
--
Øystein
