[megan_mcp]

Hi @Kal8na

This update statement seems correct, can you send me a screenshot of the error you’re receiving ?

Thanks,

Megan

[megan_mcp]

Hi @Kal8na

I’ve simplified your function and it seems to work fine. I replaced table: tables[] with just tables[].

If you have any further questions please let me know.

showTableSummary:{tables[]!{count value x} each tables[]}

Many thanks,

Megan

[megan_mcp]

Hi @Jake

There are two options you can use to load in your messages.csv file:

1. Use the Table Importer that’s located under Tools -> Table Importer (Screenshot provided)

2. Load the data from the csv into a kdb+/q table using this example from the ‘Working with Files’ section of the KDB Developer Level 2 course (Screenshot provided)

Hope this helps!

Megan

[megan_mcp]

Hi @Kenan

The problem lies with your last bit of code ‘edge > avgEdgePerOption[avgEdge]’.
You are only able to index into a dictionary, not a table. So as avgEdgePerOption returns as a table, when you run ‘avgEdgePerOption[avgEdge]’ it returns nothing (screenshot below).

This is what causes the length error as edge is a list and avgEdgePerOption[`avgEdge] is an empty dictionary.

Hope this helps!

Thanks,

Megan🙂

[megan_mcp]

Hi @lestat-jin

Thank you for reporting this bug.

Our team have been investigating this and we hope to have it resolved as soon as possible.

But as @Kenan has mentioned, it is not a permanent problem. It should resolve itself after a while.

Many thanks,

Megan🙂

[megan_mcp]

Hi @trinity

I see you have received your certificate so congratulations on completing the KDB Developer Level 3 course !

Also thank you for providing the rest of the community with a solution to this problem.

Many thanks,

Megan 🙂

[megan_mcp]

Hi @Abigail

Can you provide screenshots of where the csv file is stored and how you are trying to access it ?

Thanks,

Megan

[megan_mcp]

Hi @Kenan

Can you please download and send me your project.md file to mmcparland@kx.com so I can have a closer look?

Thanks,

Megan

[megan_mcp]

Hi @jackyyuk

At the minute, kdb+/q does not have built-in functions for bitwise and,or,xor operations. However please find below some discussions on this topic and solutions on how to provide bitwise operations.

• https://www.timestored.com/b/bitwise-operators-kdb-database/
• https://stackoverflow.com/questions/52068847/bit-shift-operation-supported-in-kdb
• https://www.mindfruit.co.uk/posts/2012/11/vectorised-bitwise-or-for-kdb/index.html

Thanks,

Megan

[megan_mcp]

Hi @thetourist

Those errors can be ignored. If you run ./setup.sh (as you have done) then head to ‘Launcher’ and launch KX Developer.

Select ‘kxsql-demo’ it should work fine.

There should be no additional steps involved. Are you experiencing this issue after following the above steps? If so, can you provide screenshots ?

Thanks,

Megan

[megan_mcp]

Hi @ismai

The correct format for tradeContext is as follows:

And can you send me a screenshot of your edgeCor dictionary so I can have a look?

Thanks,

Megan

[megan_mcp]

Hi @Kenan

The correct format for tradeContext is as follows:

[megan_mcp]

Hi @trinity

Thank you for reporting this. It has now been updated.

Many thanks,

Megan 🙂

[megan_mcp]

Hi,

The column ‘exQuality’ should not be apart of the tradeContext table. I think this may be the problem.

Megan

[megan_mcp]

Hi @ismai

Notice in your aj join you have used the tradedata and nbbodata variables instead of tradeTable and nbboTable variables.

If you adjust these, you should achieve the correct format.

Thanks,

Megan