Maintaining old pages?
When I start using MySQLi what's happening with the current pages when I maintain them? Will there be new code being generated automaticly? If I install Mysql, can I decide wich code has to be generated by the extension?
When I start using MySQLi what's happening with the current pages when I maintain them? Will there be new code being generated automaticly? If I install Mysql, can I decide wich code has to be generated by the extension?
I'm sure WA staff will answer this - but this is my experience as an end user.
Once you have installed the MYSQLi extension you will the be able to create MQSQLi connections, recordsets etc as shown in the tutorials.
Existing pages will not be 'converted' - but - you are able to move forward.
For example: if you have an old page using an existing (non MYSQLi) connection to a database, you can build a new page but this time specifying a MYSLQi conection to the same database.
You can then populate the new page with MYSQLi recordsets and behaviours and when it is working correctly, replace the old page.
I have done this a page at a time on an existing web site,
Of course all of the old (non MYLSQLi) extensions will still be there to use if you wish.
Thanks Jolter.
What if I have to change something on the "non MYSQLi" page? For example adding a new recordset. Will that one be generated with MYSQLi code? What if I only want to have "non MYSQLi" code on an "non MYSQLi" page? Do I have to run two DW version in parallel?
What if I have an older version of php on my server. Will this new MYSQLi code work?
You will still have the old MySQL server behaviors available to you to use for older pages.
If you use the standard server behaviors access points, it will generate MySQL code, if you use the access points for the MySQLi server behaviors, it will generate MySQLi code.
The system requirements for the mySQLi server behaviors requires php 5.2 or newer. so if you have a php version older than 5.2, no the mySQLi behaviors will not work.
So if I have MySQLi installed and create a new recordset on my page MySQLi code will be generated "by default"?
If I use DA for a form, MySQL will be generated.
If the new version of DA is out, MySQLi code will be generated "by default"? Means, if I maintain an old page, I will have to recreate it, when the new version/extensions are installed?
No, MySQLi code will only be generated if you use the MySQLi recordset access point.
On the server behaviors panel, click the plus button.
IF - you select Recordset - This will generate MySQL code (it is the standard DW Recordset behavior).
IF - you select web assist -> MySQLi -> Recordset - MySQLi code will be generated (this is the MySQLi recordset behavior).
Yes, this is correct
No, MySQLi code will be generated if the connection you select is a MySQLi connection. If you use a MySQL connection, it will generate MySQL code.
there is no default. It is dependent on you and the selections you make. Select to use the standard MySQL connection or standard Access points, it will use standard MySQL code.
Select to use a MySQLi connection or the MySQLi access points under WebAssist -> MySQLi, it will use MySQLi code.
Yes, this is correct.
Thank you very much for explaining me this in detail.
This was most useful - however it would be nice to put the migration process from MySQL to MySQLi in a tutorial, like the one you have on 'Getting started with MySQLi Server Behaviors'.
Please post your tutorial suggestions to the Webinar and Tutorial Topics section of the product suggestion page here:
http://www.webassist.com/community/feedback/dashboard.php
Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.
These out-of-the-box solutions provide you proven, tested applications that can be up and running now. Build a store, a gallery, or a web-based email solution.