Hello, A13x, you wrote: A> Hello, PZI, you wrote: PZI>> Hello, A13x, you wrote: A>>> There not only it, the author then added lacks and myths in the presentation - the part from them is reflected and in article: PZI>> the Author of presentation possibly specially did not show as look update through jdbctemplate. And as affairs with entity relationships are at usage jdbctemplate too concealed. And as it is easy to add/delete fields in/from in the middle, and even by the project end. A> and in what a problem? I actually do not see complexities in the type code db.update ("INSERT INTO entity (field1, field2)", val1, val2); A> Concerning removal of fields is always in a different level painfully in the grocery code, but anything outstanding I do not see. PZI>> in general, this article/presentation of the objective did not seem to me. Certainly, there are many situations where to use it is impossible, but it does not mean that the statement "do not use " which as a matter of fact is the motto of this article, truly. A> as a matter of fact article inference - usage does not give any scoring on comparing even with handwork from a DB - in itself abstraction full of holes (leaky abstraction) as it not smart enough for the full abstraction of a layer of the data, and the code the data can be written with usage of more simple and well-tried remedies. All this history with - one more acknowledgement of viability of a principle of usage of a combination of tools well ground under the narrow task against usage of the general-purpose library which can do a heap of things - in a case with there both and the data and generation of the circuit and . A> Well and after I of tears with also began to use in new projects jdbc template I categorically it do not agree that with to write the code much faster and I see it from the practical experience. A> for simple bases and simple CRUD scenarios the overhead projector of the manual code is minimum (and there is a complete control), and for difficult with it is much more than fuss. On simple examples all is beautiful. And in what attempt to read business object of 5 nesting levels having at least, including collections, and also its subsequent insert or update in basis turns. Can share best practics.