I agree that the behaviors are outdated, but as a professional level tool, having a more visual SQL editor built into DW to help write my own queries would be much more beneficial than newer behaviors.

I have never used DW Server behaviors. My observation is that most DW users are still using the older mysql extension, though of course they should upgrade. Maybe DW is waiting to follow the lead of their user-base.

I don't use DW to write any code, for the following reasons:

1. I like my own code better, my naming conventions, etc. and only use the PDO extension.

2. I use a Logitech G19 programmable keyboard which allows me to enter commonly used keyboard sequences in single keystrokes.

3. I keep a library of snippets for common code sequences that are longer than the G19 keyboard can maintain.

4. Although I don't use a framework like ZEND, my code is portable, at least across my own projects.

Therefore, if Behaviors and Spry are ways of generating sections of code quickly, I have my own personalized way of achieving the same thing, better. I have sometimes wondered if serious coders ever do use things like Behaviors, Spry, etc. Don't misunderstand me--I'm not saying that "no serious coder would use behaviors," but I assume (as someone who has never used them) that at some point every coder would outgrow them, for the kinds of reasons W3 mentions--wanting to use a database extension they don't support.

Yes, I realize my post diverged from the original focus, but the thing I did mention in the beginning is that most of the people who frequent this forum seem to still be using the original mysql extension, so Adobe may not be feeling the pressure to upgrade. Big mistake for everybody, of course. Everyone needs to stop using the old extension.

I have not used Netbeans or CODA. Not even familiar with CODA. I use ZEND studio. Yes to jQuery over spry. I don't think spry offers anything I can't just code myself, but jQuery has some very useful widgets.

I just came about this post today.

Normally I always do all my coding manually (no wizards) and I only use the mysqli versions of the php functions.

This week I was tinkering about woth CS6's Database bindings with the idea of: "It's Adobe so it could be better en easier than what I' doing".

WHAT A DISAPOINTMENT!!

I fully agree that CS6 should have moved on to the newer ad more modern mysqli behaviour/functions!!

@ Dreamweaver team: PLEASE ISSUE AN UPDATE THAT TAKES CARE OF THIS!!

(sorry for me having to shout this out loud ).

I agree. If the mySQL support is not updated to stay current, DW will die. I hesitate to build anything new in it because of this issue. RIght now, it is an expensive code editor that does not do a whole lot more for me that UltaEdit on new projects.