Re: Migration tools/plan from oracle 7.3 to Mysql 4.0With "application code", I meant 
that you:

- have to change your queries so that they include the full VIEW sql, because MySQL 
doesn't have an alternative
- have to recreate your stored procedures in application code and do you work at the 
client or a middle tier
- have to recreate all your triggers in application code to do additional work instead 
of the triggers on the database
- have to bring your checks into the application (but they won't be safe anyway, 
'cause MySQL Classic doesn't have transactions)

With regards,

Martijn Tonies
Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL Server.
Upscene Productions
http://www.upscene.com


         I had the application code. What will be the eqaulant of views in Mysql?. I 
mean in what way i have to migrate the views, triggers, stored procedures and 
contraints of Oracle to Mysql 4.0 classic version (This does not vave innodb engine).

  Thanks,
  Narasimha
  919845682459


    -----Original Message----- 
    From: Martijn Tonies [mailto:[EMAIL PROTECTED] 
    Sent: Tue 8/17/2004 3:45 PM 
    To: Lakshmi NarasimhaRao (WT01 - TELECOM SERVICE PROVIDER); [EMAIL PROTECTED] 
    Cc: 
    Subject: Re: Migration tools/plan from oracle 7.3 to Mysql 4.0




    >          Thank you for your response. Could any one give more
    clarification on the alternatives for Views, Stored procedures, triggers and
    contraints of oracle in Mysql 4.0 classic, as MySql 4.0 classic wonot
    support the InnoDB storage engine.
    >

    Well, what other alternative do you have but application code?

    With regards,

    Martijn Tonies
    Database Workbench - developer tool for InterBase, Firebird, MySQL & MS SQL
    Server.
    Upscene Productions
    http://www.upscene.com



        Confidentiality Notice The information contained in this electronic message 
and any attachments to this message are intended for the exclusive use of the 
addressee(s) and may contain confidential or privileged information. If you are not 
the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] 
immediately and destroy all copies of this message and any attachments.  

Reply via email to