[LCS]

Yes, I can confirm heavy bugs in ALTER syntax in 6.12

Seems someone has a problem with commas in loops? 😉

Hello developers, do you actually test your code from time to time?

(just look e.g. at the syntax of generated multiple “change” directives in a yog SQL while altering)

Hope you'll get that fixed pretty soon!

This version 6.12 is not very productive for me… ;(

AND, while we're at it, the moving of the ini file was a desaster *grr*

Thanx & bye,

Lcs

[LCS]

'lo webyog guys,

again I strongly recommend to investigate the following:

How many reporters of the 'sudden crash bug' have a dual core processor?

I know that other application have problems with that, especially with the AMD Dual Core

(that is my processor setup as well)…

Bye,

LCS

[LCS]

peterlaursen wrote on Oct 5 2006, 06:11 PM:

You can create a ticket if you like and 'fake' details as you like.

OK, created a ticket…

Thanx & bye,

LCS

[LCS]

I have that 'random and sudden' crash problem too,

even with the 52beta6.

Could the instability relate to dual processor setups?

[LCS]

peterlaursen wrote on Oct 5 2006, 06:11 PM:

that surprises me a lot! never heard of it before!

We will absolutely look at this!

Thanx !

Quote:

Could you post the exact configuration parameters from .htaccess

You can create a ticket if you like and 'fake' details as you like.

—

AuthType Basic

AuthName “Access for /yogdir”

AuthUserFile /my/home/is/my/castle/htpasswd

require user herbert

—

I think this is standard and works manually as well as with SQLyog.

Bye,

LCS (will be on a short vacation…)

[LCS]

peterlaursen wrote on Oct 5 2006, 12:25 PM:

it is not more powerfull than a lot of PHP-scripts. Is it?

quite 😉

If you use HTTP-tunnelling with both SQLyog and SJA I still do not understand …

OK – let me explain:

let's assume the following url for tunneling:

https://www.servername.de/yogdir/SQLyogTunnel.php

On the webserver there is a file .htaccess in the directory “yogdir”,

in which there is a http auth for directory access configured,

with user “herbert” and password “herb”.

In SQLyog you can configure all that for tunneling and it works fine.

With SJA it only works if I remove the http authentication.

Without the .htaccess user restriction SJA works fine with http AND https.

Can you please look after that? Professional users tend to (try to ;)) protect their stuff…

I reckon that tunneling with https in conjunction with http auth is a pretty decent protection?

Thanx & bye,

LCS

[LCS]

'lo Peter…

I can narrow it down: the problem with the windows sja via tunnel is the http user auth!

Of course we have an .htacces on the server in the directory containing SQLyogTunnel.php

So the windows sja works with an unprotected http/https-tunneling,

but does not with an http-auth-protected tunnel.

The SQLyog client works fine both ways!

Would be nice if that will be fixed in the near future – I have that peculiar feeling about unprotected power-scripts like your tunnel script ;)=)

Thanx & bye,

LCS

[LCS]

peterlaursen wrote on Oct 4 2006, 06:35 PM:

BTW: it could be a firewall issue too. Do you have a 'personal firewall', a router, or 'shared Internet Connection' ?

'lo Peter,

tnx for the reply. Of course we are behind a router/dmz, who is not these days? 😉

Is there a certain port to be opened?

Why does the tunneling work with the client work and doesn't work with SJA?

BTW, I used the wizard to build the job file and used the existing, working tunnelling connection as the SJA connection. Plus, I checked the jobfile, too.

Also, I of course tried the Linux SJA on the server itself. Of course it was not a problem to connect to the localhost, but here I could not send the notification mail (tried different accounts)! Is there a debugging mode or something? There's nothing interesting in *.log or *session.xml…

I'm relatively new to SQLyog but was enthusiastic about it from the first moment.

Please don't let the random crashes/disappearings, and my problem with notification jobs

be deteriorative about this 😉

[LCS]

'lo there,

I have more issues on the https thing:

the tunneling via https://… in the SQLyog client itself (5.19 Enterprise) works fine.

But when I want to use that same tunnel with sja, it always ends in an error like above:

ERROR: 1, HTTP Error. Could not connect to the tunneling URL.

For security reasons, https is the only way I can do the connection here…

Any comments?

tnx & bye,

CaBleman@LCS

LCS wrote on Oct 4 2006, 03:58 PM:

I have more issues on the https thing:

I have to correct myself: I also tested it with just “http://…”,

and the tunneling via sja.exe is not working.

Is that a known bug with sja? I know it's offtopic in that thread here now…

tnx & bye,

CaBleman

[Author]

Posts