Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Export Procedures

forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Export Procedures

  • This topic is empty.
Viewing 2 reply threads
  • Author
    Posts
    • March 13, 2006 at 4:24 pm #9532
      gordon_2
      Member

      When you export a PROCEDURE from a 5.0 or 5.1 MySQL release, SQLyog generates “DELIMITER $$;” after the DROP PROCEDURE IF EXISTS …; and “DELIMITER ;$$” after the end of the Procedure. This is the wrong form of the DELIMITER statement. If you want to use $$ as the DELIMITER It Should be “DELIMITER $$” and to set it back to the norm should be “DELIMITER ;”.

    • March 13, 2006 at 4:29 pm #20845
      peterlaursen
      Participant

      Please read http://www.webyog.com/faq/26_49_en.html

      What is WRONG and RIGHT here ? There are no standards, I believe!

      Can't you import with SQLyog?

      SQLyog does not claim to be compatible with Mysqldump in this respect!

    • March 13, 2006 at 4:50 pm #20846
      peterlaursen
      Participant

      Let me add the the DELIMITER is nothing that the MySQL server will ever know about. DELIMITER is implemented in the CLIENT only. No DELIMITER command will ever reach the SERVER (and if it did, it would cause an error!).

      So clients may implement support for this in thousands of different ways. It could be a completely graphical implementation that does not involve the word 'DELIMITER' at all (a coloring, a typography for instance)! The only thing we'll need is to find a way to describe if a statement seperator like “;” seperates INSIDE A STORED PROCEDURE CREATE-statement, or if it seperates SQL-STATEMENTS.

  • Author
    Posts
Viewing 2 reply threads
  • You must be logged in to reply to this topic.