[leahs]

Hello @chan_chenyanj,

At first glance, ‘1’ seems erroneous. I suspect a rank error when you run ‘1’ with root cause ‘iasc each col1’.

The ‘iasc‘ keyword accepts a list or a dictionary and col here is a simple symbol list and so there would be no need for ‘each’. ‘iasc’ returns the indexes needed to sort the list in ascending order.

Remove ‘each’ and step through to see the output.

Before stepping through ‘2’, is your intention to query original t, or query an updated table that you could assign to ‘1’ (currently would suspect an error returned for both cases)

I can run the code next week and explain the logic further. Fellow contributors may be able to share in the meantime.

Happy Coding.

[leahs]

Hello @yguo,

Firstly, welcome to the KX Community! Thank you for sharing your question with us.

One option that you have is in your developer plugin to define:

.axedi.plugin.preprocess: { x } // takes a string, returns a string

This is run before executing any line, and the result of this is sent on for execution (could return “” to deny execution, which will return :: ).

This will catch execution from the scratchpad, files, VI, transformer, etc.

We hope this helps you achieve your objective!

Kind regards,

Leah

[leahs]

Hello Nina,

While we have internal benchmark researchers, this may fall outside the scope of the KX Product catalogue.
I welcome the additional insight of others here that could shed light on this comparative benchmark question.

Kind regards,

Leah 

[leahs]

Hello @leguan,

Thanks for the detailed information here.

Has this user been added to the ActionTrackerUsers group?

 

Kind regards,

Leah

 

[leahs]

Thanks for highlighting @PCarroll, code.kx provides great references!

Happy Coding, 

Leah

[leahs]

Hello @suresh_kdbplus,

Great topic here! Thanks for sharing with the KX Community.

Welcoming feedback from our fellow contributors.

Kind regards,

Leah

[leahs]

Great example and will be a very useful reference going forward!

Thanks for sharing with such detail

[leahs]

Hopefully the following helps:

For every viewstate we can populate : Default and Value

When the page loads, the default field is used to populate the value field.

Therefore, here in this circumstance, we need to override the value field.

Solution:
If using a viewstate mapping we can override the viewstate value on page load.

1.  In the query editor, write a query to get the saved dictionary back from the backend
2. execute the query
3. There will be 3 tabs : Results, Mappings and Raw Output
4. In Mapping, click on the plus icon and map the value returned in the query to your dictionary viewstate
5. This viewstate will have the new value from the backend now

Thanks, 

Leah 

[leahs]

Hello Michael,

Our KX Dashboards Text Component documentation can be located here.

Specifically, the Text editor is discussed here.

Text Editor in WYSWIG mode and in HTML mode mentioned.

Lets us know if this helps you achieve your objective or not.

Kind regards,

Leah 

[leahs]

Hello @ratata

Welcome to the KX Community! The perfect place to guide you on your KDB+/Q journey.

No question is too trivial by any means.

PyKDB’s home of information is located here: https://code.kx.com/pykdb/

This home page presents links to PyKDB installation documentation, references resources that you can reach out to, offers comparisons, overviews, license information, examples and much more.

*Information for clarification – this is currently only available for customers of KX Insights.

Another link that we share on our KX Interfaces documentation is: https://github.com/brogar/pykdb – this is referenced for your convenience, but it is not a KX endorsed interface and has no affiliation with KX. *Therefore, we do not support it.

Also, here is a previous welcome post with linked resources that might be helpful when new to kdb+/q: https://community.kx.com/t5/General/Hello-folks-this-is-new-q-bie/m-p/11056

Hope this helps you!

Happy Coding, 

Leah 

*This response was edited to enhance clarification. Please refer to subsequent responses where additional resources are recommended.

[leahs]

We are interested to know what your datasource returns when the table is empty – is it an empty table with the same schema or something else? We are wondering if the table being empty means that the schema is undefined when starting and perhaps this impacts the audio alerts.

Thanks for your cooperation,

Leah

[leahs]

Given that you encounter this after a refresh, we would like to ask you to ensure that you have followed the steps below:

Here are the steps on how to allow audio on a chrome computer:

1. Launch the Google Chrome browser on Computer.
2. Click on  menu for options.
3. Select Settings from the list.
4. Scroll down to the Privacy and Security section, and select the Site settings from the menu.
5. Choose the Sounds option within Site settings.
6. Toggle the button to turn ON and allow the sound permissions.

Kind regards,

Leah

[leahs]

Hello Damian,

Thanks for reaching out here.

DC_ARCHIVE is an inbuilt file maintenance mechanism in KX Control. It allows you to archive and delete files in a Unix sense.

However, it seems clearer now (and correct me if I am wrong) that you are continuously ‘upserting’ to a flat table within the HDB daily, and your intention is to delete older rows in that table.

In this case, the archive solution is not appropriate as that is for files only.

In order to delete rows older than 7 days in that flat table, you can avail of another inbuilt process template in Control called DS_EXEC_ANALYTIC. The process template allows for scheduled execution. I have documented the implementation steps here: DS_EXEC_ANALYTIC Template

In your case, your target process will be the relevant HDB and the supplied analytic should work to delete the rows in that flat table.

Useful links for your analytic logic and for dealing with flat tables:

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

https://code.kx.com/q/ref/get/#set

https://code.kx.com/q/ref/delete/#table-rows

In summary, the archiving process template is great for managing file maintenance. However, when maintaining a flat table, we recommend the use of DS_EXEC_ANALYTIC here for scheduled execution of row removal.

Please let me know if you encounter any issues with the above or have any further questions.

Kind regards,

Leah

[leahs]

Hello @nmez9

Thank you for sharing this question with the KX Community.

Here is some feedback that we received internally:

It is not a duplication of the entity, but rather just a reference of it in more than one package.

Note the following distinction between open and solid triangles:

The triangle in general implies shared – the open triangle implies that it is shared but not defined in that package, e.g.

 

Hope this helps!

Kind regards,

Leah

[leahs]

Hello @devarsh206

Great content for our community! Thanks for sharing.

From reading the documentation, the key take home is that it is inefficient and therefore, not advised.

We welcome further feedback from our fellow community contributors.

Kind regards,

Leah