MySQLi extension and changes to WA?

HI folks, I'm just curious and a little confused about the changes in WA and how to follow the adaptations... First of all, I notice all extensions are now using Virtual instead of Require_once, in php, but that doesn't work on my servers.... Now the transition to mysqli extension... Can you explain to me what is happening, what the major differences will be and what is likely to stop functioning and will need to be updated? And why you are using virtual instead of require by default? Right now I have to manually change everything back to require to get it to work....

TIA,
Jeff

Dreamweaver will use virtual for the included files if you have your site definition set to Create links relative to the site

In the Dreamweaver site definition, you have set the "Create links relative to" option to Site, this causes Dreamweaver to use the virtual() synatx.

Change that to Document so Dreamweaver will use the correct require_once syntax.

Moving forward in newer versions of PHP, the MySQL library used to connect to the database server and process queries to return or insert / update / delete information will be deprecated. The MySQLi extension is the first step in moving toward using the MYSQLi library for database functionality.

The MySQLi extension is a replacement to the native Dreamweaver server behaviors for creating database connections, recordsets, insert / update / delete, and user authentication that have been recreated using the mySQLi library.

We will be working on upgrades to the other extensions to offer support for MySQLi in the near future.

Thanks Jason... I normally use relative to root, but had changed it for a site because one of PVII's extensions only work properly with relative definitions!

I'm glad for this new extension and it will be helpful. But since the current versions of Databridge and eCart (I assume) aren't set up for MySQLi yet, how will this extension help me or them? Won't there be a conflict in connectivity issues?

Well, the honest answer is that this extension will not help you using Data Bridge or the other WebAssist extensions right now, but is was necessary to create the groundwork first. This extension is the first step in moving to use MySQLi.

Look at it this way:
Without any extensions installed at all, there are the native dreamweaver server behaviors that can be used to create recordsets, basic insert / update /delete, and user authentication.

Those server behaviors are the groundwork that Data Bridge and the other extensions where created on.

In order to move forward using MySQLi in Data bridge and the other extensions, and because Adobe have deprecated the native server behaviors, we needed to first recreate that groundwork which is the MySQLi server behaviors extension.

With the MySQLi groundwork now created, we can move on to the next step of upgrading the WebAssist Extensions to take advantage of that groundwork.

Thanks again for the clarification. So the connection scripts used by the new extension will work. But Data Bridge when it is running through it's wizard will create its own connections? Or be able to use the one created with MySQLi?

Data Bridge will not be able to use the MYSQLi connection scripts until it has been upgraded to use MySQLi.

Will my current pages accessing MYSQL will continue to work so long as my hosting service (Google VPS) continues to use PHP 5? CAn you point me to high level information about this transition and the time?

Until the 23rd,

Nick

The MySQL library is not scheduled to be removed till PHP v6. even once PHP v6 is released, your scripts will probably still work, the host will probably not upgrade the server PHP version for some time.

Most hosts also offer an option to use an older PHP version if you ask, In 1 & 1 for example, there is a control panel option to use php v4.2 or use the Current PHP v5