Re: MIDRANGE-L Digest, Vol 7, Issue 1970

[Jon Paris <Jon.Paris@xxxxxxxxxxxxxx>]

On 6-Oct-08, at 2:17 PM, midrange-l-request@xxxxxxxxxxxx wrote:

> For instance when using PHP and MySQL you have something like:
> mysql_connect()
> mysql_db_query()

And that is exactly what you will use when you want to access via  
MySQL - which will primarily be when you are running in the PASE/PHP  
environment.

> How/where will the system understand those commands, ...

The "system" will never see them.  MySQL will see them and translate  
them into the appropriate API calls to the storage engine.

> Maybe there will be a new type of DB for the ADDRDBDIRE command, and
> when you "connect to" it will put the system in MySQL mode.

I think you are making this much more complicated than it is - or  
indeed needs to be.

The way I think of it is this.

I have MySQL running in PASE (it might as well be on a completely  
different platform)

I can choose to have the data in a particular MySQL database be stored  
in a native DB2 table. (It may also be possible to tell MySQL to use  
an existing table for its storage - not sure about that).

When I take that option I am subsequently free to view/add/delete/ 
update the data via the MySQL interface or the DB2 native (and  
assumedly DRDA) interfaces.

The native i side doesn't need anything special in the command  
interface because any access to that data is via native access  
methods.  The MySQL side just has to add the DB2 storage engine  
option.  That's it.

There are some restrictions on the way certain data is stored due to  
differences in the databases - can't recall the details.

Jon Paris

www.Partner400.com
www.SystemiDeveloper.com