Depending on what you want I agree and disagree at the same time. Assuming the developer is shielded from most complex tasks you are correct. What worries me is that each DB engine and application server has it's own best practices.Quote:
Originally posted by dknight
This is a java developer with j2ee and app server experience who has developed prepared statements and used jdbc on various OSs and at least one major relational db.
Doesn't seem that exceptional to me. Does the ad ask for admin experience for some of the skills above?
I can write SQL that will work on all these engines but I don't know enough about their internals to do it well. If you take an SQL Server developer and make him write SQL against Oracle it will work, but not in the way he intended. Each engine has it's own transactional control model, read consistency model, optimization and locking mechanisms. With this in mind can you expect someone to really claim all these skills and mean it?
Example:
SQL Server has lock escallation, whereby if a process will lock more than a certain percentage of rows in the table a full table lock is issued. By default SQL Server locks rows when you select them to force read consistency. These two facts alone mean you have to write scalable applications quite differently on each engine.
Just a thought...
