There's still 600 lines of code, where are they??

[expired user #7860]'s profile image [expired user #7860] posted 10 years ago in General Permalink
Please answer!
There's still 600 lines of code, where are they??


ps mssql, tcp
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
link - http://s43.radikal.ru/i099/1403/9f/62b0ad4363d7.png
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
ansgar's profile image ansgar posted 10 years ago Permalink
* Where is that screenshot exactly taken from?
* Which HeidiSQL version?
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
Screenshot with a base from which I work.
4720, 4727 (32 Compiled .EXE, 64 Compiled .EXE) and HeidiSQL 8.3 (25 Jan 2014) portable
ansgar's profile image ansgar posted 10 years ago Permalink
Screenshot is *where* taken from? Is it the routine editor, the trigger editor or a query tab?
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
Sorry.
Is it the routine editor!
ansgar's profile image ansgar posted 10 years ago Permalink
Ok, then what should come after the "RegistryData_KdFact,"? Probably there is a keyword which is confusing HeidiSQL's parser.
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
...case when ... ... else 1 end as RegistryData_KdFact,
case when ... ... else 1 end as RegistryData_KdPlan,
case when ... ... else 1 end as RegistryData_KdPay,
isnull(EvnPL...
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
There simple "case".
ansgar's profile image ansgar posted 10 years ago Permalink
Ok, I see. Should not be a parsing problem. Then, how big is the routine body, is it probably very huge?
Or, is there a NUL character or so at the cut position? You need to use a hex editor to find out.
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
>> Then, how big is the routine body, is it probably very huge?
1671 lines

>>Or, is there a NUL character or so at the cut position? You need to use a hex editor to find out.
I don't know.. How to do it?
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
Please, fix this bug!
TTSneko's profile image TTSneko posted 10 years ago Permalink
merelf,

until now, that can not be seen as bug in HeidiSQL. Most readers will tend to say that your script is buggy. You failed to deliver evidence that your script is okay and does not contain any dirty characters, like a NULL char or a non-system-conform CR/LF.

You were told to check with a hex editor, a matter of five minutes. That was two weeks ago, so I do not have to comment further.
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
>> You were told to check with a hex editor, a matter of five minutes.

No no no! I did not say it!
I do not know how to check this (


[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink


[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
http://s019.radikal.ru/i621/1403/27/b3ac28238dd2.png
http://s020.radikal.ru/i713/1403/44/dc24503dd065.png
kalvaro's profile image kalvaro posted 10 years ago Permalink
Am I missing something or the hexdump is from some other part of the file?
[expired user #7860]'s profile image [expired user #7860] posted 10 years ago Permalink
Another procedure, but the same problem.

Please login to leave a reply, or register at first.