orchestration_session_exec (table) Content

orchestration_session_exec (table) Schema

Start Row: 0
Rows per Page: 50
Total Rows: 2
Current Page: 1
Total Pages: 1


ORCHSESSEXID-1	De-identification	ORCHSESSID-35E5FE4B40AAD83AC08BA90D707D8009	ORCHSESSENID-09B0D9C6A65D923D93260DC4E4E9124F				UPDATE uniform_resource_investigator SET email = anonymize_email(email) executed	SUCCESS	email column in uniform_resource_investigator		De-identification completed		username in email is masked
ORCHSESSEXID-2	De-identification	ORCHSESSID-35E5FE4B40AAD83AC08BA90D707D8009	ORCHSESSENID-09B0D9C6A65D923D93260DC4E4E9124F				UPDATE uniform_resource_author SET email = anonymize_email(email) executed	SUCCESS	email column in uniform_resource_author		De-identification completed		username in email is masked

Error We are sorry, but an error occurred while generating this page. You should contact the site's administrator.

Error in query number 6:

Parsing failed: SQLPage couldn't understand the SQL file. Please check for syntax errors:

            SELECT 'text' AS component,
                (SELECT CASE WHEN $current_page > 1 THEN '[Previous](?limit=' || $limit || '&offset=' || ($offset - $limit) || ')' ELSE ' END) || ' ' ||
                                                                                                                                                   ⬆️
                '(Page ' || $current_page || ' of ' || $total_pages || ') ' ||

Backtrace

sql parser error: Expected: END, found: ' ||
                ' at Line: 42, Column: 149

"console/content/table/orchestration_session_exec.auto.sql" contains a syntax error preventing SQLPage from parsing and preparing its SQL statements.

You can hide error messages like this one from your users by setting the 'environment' configuration option to 'production'.