Views - instead of running queries against views, you will have to run 
your queries against the underlying tables. This may mean lots of changes 
to your SQL statements.  What once appeared as a single query may now have 
to be performed in multiple steps to achieve the same results.  Usually, 
this kind of redesign actually improves application performance as you no 
longer rely on a set of table abstractions which require additional 
overhead to maintain.

Cursors - Any SQL-scripted processing you did using cursors will have to 
be replaced with C/C++ routines that perform the same functions. You 
navigate recordsets according to the methods exposed by whichever library 
you use to interact with the server. Consult the documentation for the 
library you will use for specific details.

Sorry I couldn't be more exact in my descriptions but you were not very 
clear on your requirements. Please respond with more detailed descriptions 
of exactly what you need from the database and I am sure someone on the 
list can help.

Shawn Green
Database Administrator
Unimin Corporation - Spruce Pine


<[EMAIL PROTECTED]> wrote on 09/30/2004 03:24:52 PM:

> Hi,
>        Thank you for your response. Strictly we have to use mysql 4.
> 0 only. Actually the source data base is oracle 7.3, we need to 
> migrate that database to mysql 4.0 . In oracle 7.3 views/cursors are
> used. That is why i need an alternative for views/cursors in mysql 
> 4.0. We use C/C++ for Programming.  could you please explain me the 
> alternatives for views/cursors in mysql 4.0 and how to implement 
> those in mysql 4.0?.
> 
> Thanks,
> Narasimha
> -----Original Message----- 
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
> Sent: Fri 10/1/2004 12:40 AM 
> To: Lakshmi NarasimhaRao (WT01 - TELECOM SOLUTIONS) 
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] 
> Subject: Re: views/cursors in mysql 4.0

> 
> Views and Cursors are not available in MySQL 4.x.  Usually your 
> scripting language handles cursors for you (having them in 4.x would
> do you little good as stored procedures don't exist yet. Look at the
> current 5.x development for cursors and stored procedures). What 
> language do you script/program with? 
> 
> What would you like to have done with your views and/or cursors if 
> they _were_ available? Workarounds exist for almost every purpose 
> but some of them use language-specific or library-specific options. 
> 
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine 
> 
> <[EMAIL PROTECTED]> wrote on 09/30/2004 03:01:51 PM:
> 
> > 
> > Hi,
> >        How to implement views/cursors in mysql 4.0?. Normally in 
> > mysql how the selected data is maintained in the recordsets?. Is 
> > there any other alternatives to implement views/cursors in mysql 4.
> > 0?. Please advise me for the better solution.
> > 
> > Thanks,
> > Narasimha
> > 
> > 
> > 
> > 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.
> 
> 
> 
> 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