Forum Replies Created
-
AuthorPosts
-
March 28, 2007 at 5:18 am in reply to: Tunnelling On Shared Host: Extension Xml Was Not Found #23671
peterlaursen
ParticipantWe got the details.
We will continue the discussion in the ticket!
ParticipantThanks for the feedback. My apology if I 'lost balance'.
However when you worte
“Could urgent action be taken. Looks like your servers have been compromised.”
.. I just wanted to state that nothing is certain just because an AV program displays an alert.
I think it was Symantec you had most actions to take! If was new detections that raised the alert, not new code. that aleone tells that if is like an issue with the detection!
However we have learned that we will check for Nullsoft updates more frequently and before release of every stable version!
ParticipantI do not fully understand.
Do you have an issue with SQLyog 6.0 not displaying data form your local server correct?
ParticipantBy the way:
It looks like Symantec released new detections this morning!
With the latest detections there is no alert!
anybody can confirm this?
ParticipantAre there any (LONG)BLOBs in the data that you copied?
ParticipantThere is a more recent NSIS installer-builder available, that does not raise this alert.
We will build and release with this one shortly.
Also for the future we will check for new NSIS release (at least) before releasing a FINAL version!
ParticipantIt is confirmed that Norton Antivirus 2007 with detections from yesterday (2007-03-25) identifies all SQLyog installers from 5.23 onwards as the 'Virusburst' virus. NAV 2007 quarantaines those files per default.
We think it is an issue with the NAV updates from yesterday and the NSIS installer. We are working on this now. We have a few options!!
It is 100% a 'false postive' !!
Participant99.99999999 % it is a 'false positive'. Looks like new erroneous detections were distributed this night by some AV companies. That has happened once before – and the day after they corrected the error and distribuged new definitions. We had one more report this morning. We are trying to find out what happend
Note that SQLyog 5.25 has been available for 2 months, and those reports only start today! The file on the server is binary identical to what it has always been!
You do not need to be horrified, but better be informative!!! When did that happen and when did it not happen and what has changed in between? AND WHAT IS (including THE EXACT VERSION of) the antivirus software that you are using ?
ParticipantPlease upgrade to 5.26
The changelogs ( http://www.webyog.com/forums//index.php?sh…amp;#entry13161 )
say: ” Fixed a port forwarding issue with Scheduled Backup and SSH tunnel.”
March 24, 2007 at 5:45 am in reply to: Problem Synchronizing Table With Unique Key – Have To Synchronize Twic #23668ParticipantPleas always tell which program version you are using!
This “Because of the unique key constraint, the insert of (2,100,200) fails”.
Doesn't this constarint exist on target as soruce as well?
If the row exists on source it should also be possible to INSERT on target if the table CREATE statement is the same.
If the is a (server-side) CONSTRAINT on the data then of course it is not possible – but it is not a SQLyog issue then!
What am I missing?
We recently changed the order of operation for DATASYNC from INSERT -> DELETE -> UPDATE to DELETE -> INSERT -> UPDATE. That can be confusing (rows will be deleted and next inserted), but in the end data should come there.
Was it possible that you attach a small complete test case with a dump from the source as well as the target? Only one table with a few rows of data are required. I think that would the best way to secure that we do understand the problem.
You can create a ticket if you do not want to expose your data here. It can also be fake data as long as the issue is reproducable.
With FK's you should set Foreign Keys Check = 0. I repeat that the UK CONSTRAINT should not be an issue. If the row can exist on the source it should also insert on the target without problems.
Participantwe will try our best.
But it probably will not be before Monday that we have everything ready for trying to reproduce the issue
ParticipantThis was the correct place to post. so I'll delete th other post.
It is most practical to discuss only in one place.
We had quite a lot of new hardware recently and reisntalled most computers.
We therefore do not have our old Sybase install functional at the moment.
I'll have to ask you to have a little patience while we are setting it up again.
ParticipantI am moving this from the MONyog to the SQLyog category.
Personally I do not think we will honour the 'backtick removal' request. User may unawarely set it – and get errors. And next they will blame SQLyog for being a crap program generating invalid SQL. You can search and replace “`” with “” (empty string) in an editor
However 'Select all'/'unselect all' and shift-click modifiers (like gmail) are planned. Once we get past the 'unicode turbulence' we have a list of such issues that will get attention …
Participant“We're using German Windows XP Server, SP2”
BTW: this is not a server issues. It happens on the client side alone.
What is the client platform? “German Windows XP Server” = 2003(server) or XP ?
Participantplease tell what you have installed from Control Panel .. Reginal/Language Settings.
Far Eastern Langugages?
Complex scripts?
Or none of them?
I think the latter, but please confirm. We have seen those squares at several occasions in the development process, but they should not occur of course (not with only the basic languages installed either of course). They do not either on any of our systems. I do not think English vs. German OS makes any difference.
-
AuthorPosts
