Sorting a table or sorting incoming data?

[The_Bit_Plumber]

Have you defined myLogger further up in the script? If not then this wont work.

I did not. If I add the quotes around it, it should work correct?

[keithms]

I don't want to take this thread further off-topic, but a close example of SQLite in action that is familiar to everyone here is Ignition's own logs. The backing storage for these logs is a SQLite database.

[lrose]

Well that call at least should work.

Also, I edited my reply, did you see this?

@lrose

The only way I can see that rows are entered as null, is if dataOut is empty (doesn't seem likely I would expect an error, not a null entry) either way, do all of the messages have two newLines in them? for item in message.split('\n\n')

[The_Bit_Plumber]

@lrose

The only way I can see that rows are entered as null, is if dataOut is empty (doesn't seem likely I would expect an error, not a null entry) either way, do all of the messages have two newLines in them? for item in message.split('\n\n')

Yes I beleive they do, here's a code snippet of how they are formatted. It's a newline and another one back to back.

  if not found_in_aoi:
            # Print the message that the tag was identified but not in any sector
            message = f"Tag ID: {hit_name} was identified, but it is not in any sector at {formatted_time}"
        
        result.append(message + "\n")
    
    messages = "\n".join(result)
    
    return messages

the variable messages is what is used to make up the data packet.

[JordanCClark]

@Francisco.Mejia

affecting the performance of the client.

Should be alleviated with this:

@The_Bit_Plumber

Ok, so I downloaded POSTgres DB,

[JordanCClark]

Let's step back a moment. In what table is message being stored? According to the screenshot it's going into parsed_data. I would think it be saving into raw_data

[Francisco.Mejia]

You can download SQL Server developer edition which is the real thing but not to be used for commercial purposes. SQL Express is OK but has a 10 gig database limit