× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Paul Holm wrote:

> I recommend people taking a good look at SQL before creating custom code for
business problems. Just my .02.

this is generally true but it hides some dangers. First of all, when trying to put everything in SQL, you (sooner or later) automaticly have a db vendor lock in. The second problem is that you normally cant use persistence frameworks for that, or better said, you have to use the custom SQL hooks in various persistence products, thus circumventing the products cache abilities.


A good balance of SQL usage is my advice, i try to eliminate SQL usage in my development, you cant eliminate it completely, but its a goal. To me, most Java developers are better of when not confronted with too much SQL, the products can normally generate more efficient SQL code behind the scenes. I traced and monitored too much foreign JDBC code to know that most people are not experts in that area.

Marc Logemann

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.