--- title: aioc.sc _userlog slug: kronpam-how-to-guides/aiocsc-userlog description: Learn about the structure and details of a comprehensive database table designed to store commands and queries generated during a connection. This document explores the various columns featured in the table, including primary key, session ID, timestamp, c docTags: createdAt: 2022-08-18T15:35:52.000Z --- It stores commands/queries created during the established connection.   | **Column** | **Data Type** | **Description** | | -------------- | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | db\_id | bigint | Table's primary key | | session\_id | character varying(255) | Each data inserted into this table must have a session. The ID of that session is stored here as a foreign key. | | log\_time | timestamp | Date the command / query was created | | log | text | Command / query created | | allowed | boolean | The discarded query tells you if it is stuck in any Policy. "True" means it is not installed, "false" means it is installed. | | context | character varying(255) | Context name when the command is executed. | | succeeded | character | Shows whether the command has executed successfully or not.
The field is filled if the "enforcer.terminal.behaviour.error\_message\_pattern" is defined in the element type properties of the target device. | | type | character varying(255) | Application name, like SQLPROXY | | detail | text | Detail info about the executed command | | instance\_name | character varying(255) | Name of the application started by the server |