Navigation
- FAQ Home
- All categories
- About Webyog support and about this FAQ
- About the SQLyog program

- Connection issues

- Using the GUI
- Managing your MySQL Database Systems

- Database Schema Synchronization
- MySQL DATA synchronization
- SQL Scheduler and Reporting Tool
- Importing external data
- Backup/Restore
- SQLyog Job Agent (SJA)

- Working with Views, Stored Procedures and Triggers
- Character Set and Localization Issues
- MySQL bugs that affect SQLyog
- Questions on Open Source and Compiling
- Sitemap
Most popular FAQs 
- I get error 1130 "Host is not allowed to ... (168933 views)
- Error no. 2003: Can't connect... (86025 views)
- SQLyog Version History (63786 views)
- Error no. 1045: "Connection denied..." (61204 views)
- Error no. 1251: "Client does not support authentication..." (58270 views)
- Error No. 2005: Unknown MySQL server host... (50036 views)
- What is HTTP-tunneling? (42202 views)
- What Is SSH and SSH-tunneling? (37965 views)
- Can I use SQLyog with the WINE Windows emulator ... (34821 views)
- Why are Stored Procedures not created when I import ... (34230 views)
Latest FAQs 
- SQLyog Version History (2012-01-26 08:20)
- SQLyog is a client for the MySQL server - ... (2011-11-04 04:48)
- I get error 1130 "Host is not allowed to ... (2011-11-01 05:21)
- Problems on Ubuntu 11.x (2011-10-29 13:02)
- Problems creating a functional DSN on 64 bit Windows. ... (2011-09-15 14:34)
Sticky FAQs
Working with Views, Stored Procedures and Triggers
The "DELIMITER" command does not have effect. Why is that?
Before SQLyog version 5.17 we used a DELIMTER format like
Delimiter | ;
and not only
Delimiter |
That was unlike the MySQL command-line client, but the difference was because of the general difference of a command-line tool and a graphical editor. With a graphical editor a linebreak is "parsed away" so you must somehow tell the system that end-of-statement has been reached. You did that with the old delimiter. So the 'mysql' command line client (and other programs from MySQL AB) would not execute SQLYog DELIMITERs and vice-versa.
However from SQLyog 5.17 both formats are supported (and the 'short' one is default). We complete rewrote the parser/tokenizer component of SQLyog to enable this, so this issue should not occur anymore.
Tags: -
Related entries:
- SQLyog Version History
- What kind of ODBC databases are supported by SQLyog Import External Data Tool?
- Error no. 1045: "Connection denied..."
- Error no. 2003: Can't connect...
- UPPERCASE in table names are LOWERCASE'd
Last update: 2006-09-06 23:10
Author: Peter Laursen
Revision: 1.3
You can comment this FAQ