> If I recall correctly, the dbi_read_only flag only applies to a database
> instance's ability to be written to disk. So in-memory database instances
> are inherently "read only" since they should never end up calling db_write.
> I believe dbi_read_only is set to true merely as a "just in case" sanity
> measure.
>
> It works because in-memory operations happen before file operations. The
> dbi_read_only check only prevents the latter from occurring. Additionally,
> for your specific example, nothing has been written to the inmem dbip yet
> besides the ident header which bypasses read-only checks since it's a very
> low-level preparation activity anyways.
>
> To make any read-only database instance a writable instance, you merely set
> the dbi_read_only flag to false. I can't think of a reason that in-memory
> databases couldn't have dbi_read_only be set to false by default, but it
> wouldn't/shouldn't change anything.
It does make a difference. Try to set the database title in my
example. I.e. put db_update_ident(inmemDb, "The New Title",
inmemDb->dbi_base2local); right before the db_dump function. To make
this work you have to set "inmemDb->dbi_read_only = 0;".
Sziasztok,
Daniel
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
BRL-CAD Developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
