I’m looking for an efficient way to save an object array queried from a sql database directly into Tulip tables as a series of new records.
There must be a way to do this directly without deconstructing the object array into multiple child arrays and then looping through the multiple child arrays to create a series new table records, but I am having difficulty finding any documentation on this use case. Where can I find it? Thanks!
Tulip currently does not natively support object storage and interaction in Tables.
At this moment the only solution is to use an expression and wrap the object with a TOTEXT() function to write a JSON of the object. This can be stored in a text column.
You will then need to use custom widgets or an intense combination of formulas to parse and unpack the string.
It would be really cool if Tulip connectors could do this parsing for us. Preventing the need for custom widgets.
@Pete_Hartnett is there any way to parse a JSON string like so? This would allow you to write objects to a text column and then build a connector to extract them later.
This would be a very useful functionality. My initial aim was even lower, though. If I have a Tulip table with, let’s say, three columns: [orderID (string), datetimeCreated (date time), isCompleted (boolean)] and I want to pull new orders over from a SQL db via a SQL connector, my SQL connector will output an object array with types string, bool, datetime. I want to save that object array into my Tulip table with the compatible columns and data types. Can Tulip support this?
No, Tulip can only write records one at a time so all of the solutions here will require iterating.
Is there a feature flag that must be turned on to enable read/write of tulip tables via custom widgets?
Similar to:
tulip.tables.getTableByName(“TestTable”);