Hello, Thanks for the feedback and sorry for the delay
2013/5/26 RIT <[email protected]> > From your description it looks like you hope to unify the whole CRUD cycle > against the Result/Record objects. > > > My first thoughts are – if you can do it without it taking up all your > free time and limiting your future plans it would be rather nice as to work > with a database row all you would do is work with a single Java object. > Time hasn't been of the essence so far, in this project :-) > As for there being maybe only a few users, I think that may come about > unless you make it very clear the availability of this feature. The reason > being is that few people will expect such a feature to be available and so > would not go looking for it. > That's precisely what I think. > One of the comments from igor about 'a resultset that is capable of > updates just feels heavy' in a world of high load websites also indicates > that these type of features will need to be targeted and explained. My > background is far more from the 'heavy' end of the SQL world so a resultset > that is capable of updates seems like a good way for me to focus more on > the SQL and less on the Java code. > Exactly. Igor has created several libraries, including ActiveJDBC but also ActiveWeb. His focus is mainly on developing tools for efficient website development. jOOQ has always had a more SQL-centric focus, than a Java one. So I think that operating on rows, records, result sets, cursors, etc. will not feel wrong to people with a SQL background. After all, some dialects (e.g. T-SQL, PL/SQL) implement extensive row operations in their procedural language parts as well. Cheers Lukas -- You received this message because you are subscribed to the Google Groups "jOOQ User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
