RE: [personal kdb+] Abridged summary of

Community Support
1

 

Thanks Caolan,

I appreciate the follow up. I managed to get things working, so thanks for the help.  I also found the following works in sending entire scripts by reading and razing the text from a .q file.

 

Follow up question – what I noticed is I have to remove all comments from my for it to work properly  (i.e. no // prefixed lines even if I include a semi-colon.)  While it works, it would be ideal to leave comments in the code for auditing  Am I missing something regarding the comments?

Many thanks again!

Charles

Jason

 

 

\p 5042 h:hopen :XXX.XXX.XX.XX:5042 funcs: raze read0[$“./Functions/MyFunction.q”] /(Note** - I had to remove all comments from my function code fyi as it didn’t like // at all.) h funcs hclose h

 

 

 

 

 

 

 

|

Devon McCormick : Oct 24 06:32PM -0400

Thanks for the help. I may look at the Fourier transform if what I have is
too slow but I want to complete the process all the way to the end before I
worry about optimizing it. Does anyone have …more

 

 

|

|

Caolan rafferty : Oct 24 03:23PM +0800

Hi Jason,
 
You can pass function definitions across IPC like so:
 
q)func:{x+y}
q)h:hopen 5555
q){h({x set y};x;value x)}each value “\f”;
 
Thanks,
Caolan
 

|

 

 

 

 

|

Alvi Kabir : Oct 22 08:52PM -0700

Another approach: Build up column dictionary and pass it into functional
update:
 
q)show t:(date:.z.d-til 100;close:100?100f)
date close

2020.10.23 54.97936 …more

 

 

|

 

 

 

 

 

 

 

 

2

Hi Charles,

You can read any remote file/script in as a byte stream using ‘read1’ and then subsequently use ‘1:’ to write this byte stream to a local file (along with comments)

q):local_script.q 1: :hostname:port"read1`:remote_script.q"


Regards,


Connor

""?