Re: [Modeling-users] SQLite inserts slow
Status: Abandoned
Brought to you by:
sbigaret
From: Ernesto R. <er...@si...> - 2004-06-30 14:42:00
|
Hi, Yes, I have the same opinion as Mario: 1. the adaptor (name) to be used should not be part of the model, but read in vía config. file, although I know that code generation is a bit different for each db adaptor. (I hope that soon dynamic will get a big push and within a year everyone uses dynamic, so we have no code generation phase: just change the config file and reinit the application, and voilà, you use another database backend.) 2. there should be hooks on a per db adaptor base (at least, at db creation time, and at connection time). Perhaps, which instructions to send to the database should be part of either a general config file with a section for each db adaptor, or a different config file for each db adaptor. With best regards, Erny Mario Ruggier escribió: >> While we're at it, are there other PRAGMAs that you all using >> sqlite think they should be controlled in the same way? > > > I have not played with sqlite pragmas, so none that I can think of. > But, this makes me think of another minor issue... given that the > adaptorName is specified in the model, should there not be a place or > hook to specify any adaptor/db-specific initialization sql/code? > > Or, stated differently, should not adaptorName be specified in the > config file, along with the connection dictionary? And, should not the > config file contain or point to sql or other code to be executed on > specific events, such as when db is created, when connection is > established, etc. This flexibility, while it may risk being abused > ;), could avoid getting stuck by the frameworks limitations at any > given moment.... > > mario > > > |