How will MySQLi impact current plugins?

If MySQLi is a complete new way to make DB Connections, queries, repeat regions etc... I am curious how it is going to interact with your current extensions. Many of your extensions connect with a database, with Data Assist and eCart likely the two flagships.

1: With they currently work with a MySQLi connection?
2: If not, what is your "roadmap" for making all of your extensions compatible with MySQLi.
3: Do you have plans to support both MySQLi and MySQL moving forward with your extensions, or is everything going to move over to MySQLi.

I see a very large grey area taking shape in regards to your extensions, and am just curious what direction Web Assist is planning on taking so I can better plan my own strategies.

This post has been deleted.

I think it is very important that they update their current extensions to use MySQLi ... but I also hope the updates will continue to work with the deprecated MySQL extension so users can choose the way they want to work and continue to maintain older sites. When a feature is deprecated it is very important to provide the alternative early and I thank WA for jumping on this for us.

If you rely on a web host of any sort (ie: do not use a self-managed server) then you need to be even more concerned. It may not happen for a couple years - but sooner than later scripts will stop failing completely if you are not using MySQLi or PDO.

I am very cocerned as well - please explain the impact - do i have to rebuild all of my websites ? Does your mysqli extension fix everything or will i have to buy new versions of ecart and bridge ?

The MySQLi Extension is the groundwork that was needed to be laid for starting the MySQLi migration.

Think of it this way:
For the existing extensions, The DW Server behaviors where the groundwork they where built on. Adobe has depreciated the server behaviors, so we first needed to recreate that ground work which is the MySQLi extension.

Now that the MySQLi extension is released, we will be starting to work on migrating Data Bridge, Design Extender and eCart.

Data Bridge is the first one we will start on. as it is the most database driven of the extensions it will take the most time to complete.

Jason - Web Assist does great work, and I love the products, but this release seems terribly unplanned.

1: You are selling a new product that is not compatible with any of your current extensions.
2: You are not setting any clear timelines of when the other extensions will be updated.
3: You are not informing anyone if those extensions will be backward compatible or not, or if they will be a free update, or a paid upgrade.

If you update "one extension at a time" how is that going to work? Data Bridge will be MySQLi, eCart MySQL... Until all are done - I can't use any. It's a logistical nightmare of incompatible code. As much as I like this entire decision to go MySQLi, I'll have to completely ignore this new extension until you have solidified your positions because I cannot prepare any future business strategy based on the lack of information.

Just speaking my mind :) (but will continue to use your great products...)

It's not that it is unplanned, but that it is a big job that cannot be done all at once and, as such, the plan is a long term one.

The MySQLi extension is the first step that was needed to make the migration, the other steps will follow.

As the other extensions are upgraded to offer MySQLi support, they will still be backwards compatible with previous pages that are developed using MySQL.

Rome was not built in a day, neither was the migration to MySQLi.

We have not made any final determination on what features will be included in the MySQLi upgrades to the other extensions, or any upgrade pricing.

I find it nice that WA is releasing the MySQLi server behaviors early so that users can already start using the basic data functions and informing those who have Data Bridge, Ecart or Super Suite to upgrade. Though I think this might be two of the concerns with regards to MySQLi and the other plugins
- Will MySQL Server Behaviors become redundant once a DataBridge with MySQLi version is available? Apart from recordset creation all other features are in Data Bridge
- For those willing to be early adaptors of MySQLi plugin will there be another upgrade cost once a full Data Bridge version with MySQLi is available (To those who purchase MySQLi Server Behavior now and already have Data Bridge)

The MySQLi server behaviors will become a part of Data Bridge when it is upgraded.

If you purchase the MySQLi server behaviors extension now, the cost will be deducted from the upgrade cost when the Data Bridge upgrade is released.

Hi Jason,

Are you able to give us a rough indication on when the upgrade to Data Bridge is expected?

Thanks,

Shaun