Introducing ErlyDB: The Erlang Twist on Database Abstraction
Wed Aug 30 21:35:12 CEST 2006
On 8/30/06, Yariv Sadan <yarivvv@REDACTED> wrote:
> The Erlang code is generated just once, when you call erlydb:code_gen.
> This generates the entire abstraction layer on the fly. The idea is to
> call erlydb:code_gen once when you boostrap your app and then every
> time you make a schema change to your database. No code is generated
> at request time.
Just a thought: regenerating the code at run-time when the schema
changes is dangerous. Unless the change is trivial, any client modules
would need to be updated too.
IMHO it might be better to do the generation at compile time so that
all changes can be caught and corrected before deploying the whole
system at once.
BTW, a non-trivial schema change can't be handled without taking the
system down anyway, so maybe the above is not helping much :-) The
important observation is that there's much more to think about than
just generating the abstraction layer.
More information about the erlang-questions