We encountered no real problems when converting a database from Interbase, with some
stored procedures and triggers as well, to mysql.
Most stored procedures were for things like generating a unique key, getting the
server date/time/year, etc.
Triggers are imho just application _unfriendly_, since the programmer has no influence
on triggers in the database, unless he/her alters them, which can be quite annoying.
Maybe your application(s) need some extra lines of code, but personally i do not see
this as a limition. Our app was in fact, with some minor issues, fully compatible with
mysql (it's a compiler switch now :)).
regards,
rene
On Tue, 24 Apr 2001 11:39:55 -0400 (EDT)
Istiaque Hussain <[EMAIL PROTECTED]> wrote:
> Dear Friends ,
>
> One of our clients wants to port the Database which was originally in MS SQL , to
>MY SQL . he main problem we are facing is that how to make previous stored procedures
>run . There are a lot in the application . Front end was in VB .
> We are now into feasibility study . Please give information on that .
>
> Bablu
>
> ______________________________________________________________
> Ayna, The Arabic Internet Starts Here. http://www.ayna.com
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
