

megan_mcp
Forum Replies Created
-
megan_mcp
AdministratorMarch 25, 2024 at 11:18 am in reply to: Failed to start workspace for SQL courseHi @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
AdministratorMarch 25, 2024 at 11:00 am in reply to: Capstone 3.1 and 4.7 Format is incorrectHi @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
AdministratorMarch 21, 2024 at 11:08 am in reply to: Programming language used in Dashboard GUI -
Hi @trinity
Thank you for reporting these mistakes.
We will update this so that the course is accurate.
Many thanks,
Megan
-
-
Hi @may
Please see attached some documentation/blogs that might help with the topic of partitioning tables.
Partitioning Data in kdb+ | KX
Partitioned Tables – thinq-kdb (wordpress.com)
Partitioned tables | Knowledge Base | kdb+ and q documentation – Kdb+ and q documentation (kx.com)
Thanks,
Megan
-
Hi @mario
This article should prove to be useful – Containerizing kdb+ with Docker. Making kdb+ portable and scalable | by Aidan O’Gorman | Medium
If you have any issues, please let me know!
Thanks,
Megan
-
Hi @utsav
It looks to me like you might not have created an API key yet.
To double check this, goto the KDB.AI portal under Connection Details -> API Keys.
If you have any more issues please feel free to let me know.
Many thanks,
Megan
-
Hi @masmail
The certificates get sent out every hour so it could have just took a minute but I see you have received it so congratulations on completing the course!
Thanks,
Megan
-
megan_mcp
AdministratorMarch 20, 2024 at 12:54 pm in reply to: Functional Statement Exercises in KDB+/Q Developer Level 3Hi @trinity
Thank you for letting us know, as always we will make sure to update this immediately so that it is accurate for future users.
Many thanks,
Megan
-
Hi @trinity
Thank you for reporting this.
We will adjust this so that it is accurate.
Any more issues feel free to let us know!
Many thanks,
Megan
-
Hi @masmail
I’ve noticed a few things from your screenshots:
If you take a look at the challenge.quke file, you will see the correct answer should be as follows (screenshot below). So you don’t seem to have the correct values.
The problem lies in your table join. To be able to join two or more tables, you must use a related column. In this case our related column is ‘student_no’.
To do this I’m going to use an INNER JOIN:
"INNER JOIN students ON results.student_no = students.student_no"
Also to achieve the correct value when rounding I advise you use ROUND instead of FLOOR.
Hope this helps!
Thanks,
Megan