csm | The C Scan Matcher

Try running the recursion within csm:

Now proper output is coming. i made some changes in sql. here is working code.

OK... I'm sorry, but this is a bad answer. A really bad answer. It's the type of answer when you need a fix right now, and don't have time to fix the problem properly.

The true fix is to exclude the rows that have no valid values before combining them into the data set used to create your table. However, without knowing your processes/data much more intimately, I cannot do this. Instead, I have a complete hackjob.

Anyway, from what I can tell

• In the table #TmpZacksCons
• You have some rows where all the columns relating to dates are all NULL
• And you would like to exclude those
• The column names are set dynamically - they are in the variable @PeriodCols

What you can do is to delete the rows from #TmpZacksCons that have all NULLS. The problem is, of course, that those columns are dynamically created.

So, after your existing command

Short version

The ORDER BY is doing what is expected - ordering first by ID, then Ord, then BM_Code, then LineItem, then BrokerName.

Within ID 76187, the next field to order by is Ord - which it sorts from 30911, to 31097.

If it previously ordered by BrokerName, it was only by chance - or that Ord was ordered the same way as BrokerName.

My initial suggestion is to re-order your sort e.g., ORDER BY ID, BM_Code, LineItem, BrokerName, Ord

Longer explanation of issue

In SQL, underlying data is treated as a set and ordering doesn't matter.

For example, if you have a variable @x and you were testing IF @x IN (1,2,3,4,5) will produce the same result as IF @x in (5,4,3,2,1).

In your example, you're putting an ORDER BY into the sub-query you're checking with the IN e.g., ORDER BY ... BrokerName IN (SELECT BrokerName FROM #Brokers ORDER BY BrokerName ASC). The order of that sub-query isn't allowed, and wouldn't do anything anyway.

The only sort that matters (other than for a few things like TOP) is the final sort - when displaying the data.

That being said, even if you removed the ORDER BY in the sub-query, it wouldn't help you with your issue

• The SQL is not likely to work anyway - ORDER BY needs a value - you may have needed to make it CASE WHEN BrokerName IN (...) THEN 0 ELSE 1 END
• Which also won't help, as the issue is that Ord is sorted before BrokerName anyway.

UPDATE following comment

Fundamentally, the statement that provides the actual report is

Do you by any change use PackageManager object? I've had the same issue and it turned out there's a weird bug using this object, if you are using it too much it may "die" and cause your app to also receive a "dead object exception". If not, I'd recommend you try to comment out lines that you might have added prior to this exception and try to figure out what is causing that issue. Also, if it's possible to provide us with code, that would help

Ok, so I figured out what my problem was.

ncurses getstr returns a binary value, and I was sending it to a string literal variable.

I created a new set of variables, set them up as

header=0 means to take first line of csv as column names, if you need pandas to auto-numerate column names then you need to pass header=None. Also as now you need probably to skip first csv row with foreign column names you should also pass second param skiprows=1.

All you have to do, if I get your question correctly, is to do this :

The issue was actually that the same module was loaded with different paths. So my foreign key didn't refer to the correct table.