forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Delimiter In Sqlyog
- This topic is empty.
-
AuthorPosts
-
-
September 24, 2005 at 8:44 pm #9252peterlaursenParticipant
3 small issues:
1) What I wrote here
http://www.webyog.com/faq/25_49_en.html
… does not seem to be correct as of SQLyog beta2
DELIMITER-change must be DELIMITER //; and not DELIMITER // ;
No blank character (or a line-break) is allowed between new and old DELIMITER. Is that a necessary restriction? If yes, the FAQ should be adjusted accordingly!
2) Is it absolutley necessary to use DELIMITER //; when script is running from a file (“tools .. import from SQLdump” in SQLyog). I think that some people might have scripts in stock (that they use from applications for instance) for using only DELIMITER // and I think that those scripts should run. There is no need to “lex” and “parse” the end-of-line away when running from a file. But it is a coding issue, and you can better tell your reasons. For total compability I actually would prefer that DELIMITER //; and DELIMITER // both worked from editor and from file.
3) I'd prefer that “import from SQLdump” was changed to “exetute file with sql-statements” because the SQL does not need to be a dump. It can be any SQL.
-
September 25, 2005 at 5:00 am #19285RiteshMemberQuote:No blank character (or a line-break) is allowed between new and old DELIMITER. Is that a necessary restriction? If yes, the FAQ should be adjusted accordingly!
Currently yes. I will fix this issue in BETA 3 or 4.
Quote:Is it absolutley necessary to use DELIMITER //; when script is running from a fileYes.
I have added this issue in TO-DO list. We will fix it by 4.2 FINAL.
Quote:I'd prefer that “import from SQLdump” was changed to “exetute file with sql-statements” because the SQL does not need to be a dump. It can be any SQL.I will discuss it with my fellow people and do accordingly 🙂
-
-
AuthorPosts
- You must be logged in to reply to this topic.