[rocuinneagain]

If you have a q process which is able to use TLS then you can compare the output of it’s -26![] with the output of pykx.ssl_info[] in Python. This often shows what differences are causing the problems.

• https://code.kx.com/q/basics/internal/#-26x-ssl
• https://code.kx.com/pykx/1.6/changelog.html#pykx-140

 

[rocuinneagain]

If you have a q process which is able to use TLS then you can compare the output of it’s -26![] with the output of pykx.ssl_info[] in Python. This often shows what differences are causing the problems. – https://code.kx.com/q/basics/internal/#-26x-ssl – https://code.kx.com/pykx/1.6/changelog.html#pykx-140

[rocuinneagain]

This blog will have useful information:

Explore the methodology and benefits of kdb+ Memory Mapping | KX

[rocuinneagain]

For 3. the suggestion is to test in a browser. A q connection to the python server would fail as the protocols are different.

[rocuinneagain]

If python is running a server but your browser cannot connect it suggests an issue with the network settings and not kdb+. Are only certain ports open?

 

If I can only use ssh port I often set up a port forward so I can connect on my machine

https://linux.die.net/man/1/ssh#:~:text=%2DL%5Bbind_address%3A%5Dport%3Ahost%3Ahostport

 

ssh -L 6154:localhost:6154 whateveryourusernameis@10.106.4.131

 

 

[rocuinneagain]

Use `$ to cast a string to a symbol

https://code.kx.com/q/ref/cast/

 

`$":file-with-dash.csv"

 

 

[rocuinneagain]

Could you format you code. This will make it easier for others to read/understand it so that they can help.

[rocuinneagain]

1. Is it possible you have some firewall/networking rules blocking remote access?
2. Can you open  10.106.4.131:6144 in your browser?
3. Can you try something other than kdb? .i.e python3 -m http.server 6144 and connect your browser.

[rocuinneagain]

.Q.chk adds missing tables, not missing columns.

https://code.kx.com/q/ref/dotq/#chk-fill-hdb

 

Use addcol in kdb/utils/dbmaint.md to add columns.

Note: this will write to all partitions so ensure you do not overwrite valid data.

 

https://github.com/KxSystems/kdb/blob/f06c97784b0859517a8461d76607c07a47458ae5/utils/dbmaint.q#L11

add1col can be used instead to choose which partitions to write to.

[rocuinneagain]

It’s expected that you cannot run pykx.q(‘1+1’) when in unlicensed mode. Can you try again for licensed mode after making a copy of:C:UsersAmod Shankeranaconda3envspython396python.EXE The copy should be python3.EXE:C:UsersAmod Shankeranaconda3envspython396python3.EXE + just to confirm: 1. How did you install PyKX? 2. What version have you installed? pykx.__version__ or view it in conda list

[rocuinneagain]

Does the import work in unlicensed mode? set QARGS=”–unlicensed”

[rocuinneagain]

As well as a licence expiry date each kdb+ licence also has a maintenance update date. licence expiry: You cannot use kdb+ after this date gives exp error maintenance update expiry: You cannot use versions of kdb+ newer than this date. Gives upd error https://code.kx.com/q/basics/errors/#:~:text=format%20not%20recognized-,upd,-Function%20upd%20is .e.g if you have a maintenance expiry date of 2021.12.31 but a licence expiry of 2022.06.01 this means you can use kdb+ up to 2022.06.01 as long as the version of kdb+ was released before 2021.12.31 The dates of your licence are included in the email you got from licadmin@kx.com As of 1.6.0 PyKX is based on 2023.04.17 version of q https://code.kx.com/pykx/1.6/changelog.html#pykx-160 To get a new license with a more open maintenance expiry date your designated contact can reach out to licadmin@kx.com to have a new license issued: https://code.kx.com/q/learn/licensing/#commercial

[rocuinneagain]

I’ve corrected my link. You specifically need the insights free trial license to get the flags: https://kx.com/kdb-insights-personal-edition-license-download/

[rocuinneagain]

Updating that link to download with PyKX flags must be done using the insights link specifically: https://kx.com/kdb-insights-personal-edition-license-download/

[rocuinneagain]

You license will need the flags insights.lib.embedq and insights.lib.pykxto run pykx.q You can check your license flags in q using: q).z.l 4 “insights.lib.embedq insights.lib.pykx insights.lib.sql insights.lib.qlog ins.. If you have an older trial license you simply need to request a new one at: https://kx.com/kdb-personal-edition-download/ https://kx.com/kdb-insights-personal-edition-license-download/ Then replace the old with new on your machine. New licenses come with all the flags enabled. If it is a commercial license then your designated contact can reach out to licadmin@kx.com to have a new license issued: https://code.kx.com/q/learn/licensing/#commercial