Forum Replies Created
-
AuthorPosts
-
RiteshMember
Sorry but we are not able to reproduce the error with SQLyog v4.05 or v4.06 BETA 4.
Can you mail me sample data with a query and screenshots of your escape character window?
Note: While working on the report, we came across another bug where the option Field enclosed by optionally… behaves incorrectly. We will be releasing v4.06 BETA 5 soon that will have the bug-fix.
RiteshMemberI have forwarded the issue to my development team.
If its a bug then it will be fixed in the next BETA of SQLyog v4.06.
RiteshMemberQuote:did you change something with the code in Beta4. I don't think I can reproduce the exact behaviour of beta3!Or maybe it's just my poor head that needs to rest
Nope. We have not changed anything between BETA 3 and 4 with respect to this issue.
Quote:But problems with INSERTs and UPDATEs are unchanged with Beta4.We plan to fix this issue in v4.1
Quote:BTW: when will pic upload work again ???Very soon. We are working on the issue.
RiteshMemberThe current version support sorting on table data view tab.
Client-side sorting on resultset will be added in v4.07.
RiteshMembermattyb wrote on May 2 2005, 01:51 PM:I unchecked “create bulk insert statements”, redid the dump and then imported – worked. Table names have been changed to lower case but what should I expect on a Windows machine. The import did take a while though : 5M file and about 30 mins (the file was already on the PC running Windows XP and MySQL).I'll edit the my.ini for the packet sizes.
Thanks for your help Peter.
Matt
Thats very strange.
It should not take so much time.
If the data is not confidential then can you send me a dump of your database?
RiteshMemberConfirmed!
We will be releasing BETA 2 that will have the fix.
RiteshMemberv4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberv4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberpeterlaursen wrote on Apr 26 2005, 10:37 PM:There is a small bug too.ALTERing tables with a TIMESTAMP field from sqlyog produces this code
alter table `test`.`tablename1` ,change `mytime` `mytime` timestamp DEFAULT 'CURRENT_TIMESTAMP' NOT NULL
should be
alter table `test`.`tablename1` ,change `mytime` `mytime` timestamp DEFAULT CURRENT_TIMESTAMP NOT NULL
String 'CURRENT_TIMESTAMP' is illegal as a timestamp!
v4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberv4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberv4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberv4.06 BETA has been released. Check http://www.webyog.com/forums/index.php?act…&st=0#entry5252 for more details.
RiteshMemberQuote:Will the cross platform release in 6 months be able to specify a CA cert/client certificate and key to [SQLyog Max BETA2] thus enabling a ssl connection to a mysql database in the unix environment?We have not yet decided on this issue. I have to talk to my development team.
Quote:Will the cross platform release in 6 months have support for mysql 5.x including stored procedures/triggers (assuming 5.x is out of beta at that time)?This feature is already planned for SQLyog v5.0. It will take more time for SQLyog Yogmax BETA to have the above features.
RiteshMemberThanks for the report.
I have forwarded it to my development team.
-
AuthorPosts