::warning file=examples/Core-G-1010.sql,line=4,col=4,endLine=4,endColumn=9,title=Core G-1010%3A Try to label your sub blocks.::Missing start label in sub block.
::warning file=examples/Core-G-1010.sql,line=6,col=4,endLine=6,endColumn=7,title=Core G-1010%3A Try to label your sub blocks.::Missing end label in sub block.
::warning file=examples/Core-G-1010.sql,line=8,col=4,endLine=8,endColumn=9,title=Core G-1010%3A Try to label your sub blocks.::Missing start label in sub block.
::warning file=examples/Core-G-1010.sql,line=10,col=4,endLine=10,endColumn=7,title=Core G-1010%3A Try to label your sub blocks.::Missing end label in sub block.
::warning file=examples/Core-G-1020.sql,line=9,col=8,endLine=9,endColumn=24,title=Core G-1020%3A Always have a matching loop or block label.::End label 'data_preparation' does not match start label 'prepare_data'.
::warning file=examples/Core-G-1020.sql,line=15,col=13,endLine=15,endColumn=23,title=Core G-1020%3A Always have a matching loop or block label.::End label 'while_loop' does not match start label 'process_with_while_loop'.
::warning file=examples/Core-G-1020.sql,line=20,col=13,endLine=20,endColumn=23,title=Core G-1020%3A Always have a matching loop or block label.::End label 'basic_loop' does not match start label 'process_with_basic_loop'.
::warning file=examples/Core-G-1020.sql,line=25,col=13,endLine=25,endColumn=21,title=Core G-1020%3A Always have a matching loop or block label.::End label 'for_loop' does not match start label 'process_with_for_loop'.
::warning file=examples/Core-G-1020.sql,line=23,col=16,endLine=23,endColumn=18,title=Core G-4395%3A Avoid hard-coded upper or lower bound values with FOR loops.::Hard-coded upper bound value 10 in FOR loop.
::warning file=examples/Core-G-1020.sql,line=24,col=7,endLine=24,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-1020.sql,line=30,col=13,endLine=30,endColumn=28,title=Core G-1020%3A Always have a matching loop or block label.::End label 'cursor_for_loop' does not match start label 'process_with_cursor_for_loop'.
::warning file=examples/Core-G-1020.sql,line=29,col=7,endLine=29,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-1030.sql,line=6,col=7,endLine=6,endColumn=19,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable l_first_name.
::warning file=examples/Core-G-1030.sql,line=7,col=7,endLine=7,endColumn=13,title=Core G-1030%3A Avoid defining variables that are not used.::Unused exception e_good.
::warning file=examples/Core-G-1040.sql,line=6,col=7,endLine=6,endColumn=12,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1040.sql,line=14,col=25,endLine=14,endColumn=29,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1040.sql,line=21,col=22,endLine=21,endColumn=31,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1040.sql,line=33,col=14,endLine=33,endColumn=19,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1040.sql,line=37,col=7,endLine=37,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-1040.sql,line=38,col=21,endLine=38,endColumn=25,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1040.sql,line=39,col=7,endLine=39,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-1040.sql,line=42,col=4,endLine=42,endColumn=11,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-1050.sql,line=5,col=39,endLine=5,endColumn=41,title=Core G-1050%3A Avoid using literals in your code.::Literal 10 is used 3 times.
::warning file=examples/Core-G-1050.sql,line=3,col=29,endLine=3,endColumn=30,title=Core G-7310%3A Avoid standalone procedures – put your procedures in packages.::Put p in a package.
::warning file=examples/Core-G-1050.sql,line=8,col=1,endLine=8,endColumn=4,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of procedure p.
::error file=examples/Core-G-1060.sql,line=13,col=11,endLine=13,endColumn=16,title=Core G-1060%3A Avoid storing ROWIDs or UROWIDs in database tables.::Storing ROWID in employees_log.
::error file=examples/Core-G-1060.sql,line=13,col=11,endLine=13,endColumn=16,title=Core G-2190%3A Avoid using ROWID or UROWID.::Avoid using rowid.
::warning file=examples/Core-G-1070.sql,line=4,col=19,endLine=4,endColumn=43,title=Core G-1070%3A Avoid nesting comment blocks.::Nested comment -- nested comment two */.
::warning file=examples/Core-G-1070.sql,line=6,col=21,endLine=6,endColumn=46,title=Core G-1070%3A Avoid nesting comment blocks.::Nested comment /* nested comment four */.
::error file=examples/Core-G-1080.sql,line=9,col=11,endLine=10,endColumn=28,title=Core G-1080%3A Avoid using the same expression on both sides of a relational comparison operator or a logical operator.::Expression 'emp.salary > 3000' used on both sides of the condition.
::warning file=examples/Core-G-1110.sql,line=5,col=1,endLine=5,endColumn=7,title=Core G-7125%3A Always use CREATE OR REPLACE instead of CREATE alone.::Missing OR REPLACE in create statement.
::error file=examples/Core-G-1110.sql,line=5,col=26,endLine=5,endColumn=27,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::error file=examples/Core-G-1230.sql,line=4,col=24,endLine=4,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1230.sql,line=10,col=23,endLine=10,endColumn=30,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for child_id.
::error file=examples/Core-G-1240.sql,line=4,col=24,endLine=4,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1240.sql,line=10,col=23,endLine=10,endColumn=30,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for child_id.
::error file=examples/Core-G-1250.sql,line=5,col=24,endLine=5,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1250.sql,line=11,col=23,endLine=11,endColumn=30,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for child_id.
::error file=examples/Core-G-1260.sql,line=4,col=24,endLine=4,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1270.sql,line=4,col=24,endLine=4,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1280.sql,line=4,col=24,endLine=4,endColumn=31,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::error file=examples/Core-G-1310.sql,line=6,col=1,endLine=6,endColumn=4,title=Core G-1920%3A Avoid syntax errors.::no viable alternative at input 'begin\n null\nend'
::notice file=examples/Core-G-1910.sql,line=4,col=36,endLine=4,endColumn=43,title=Core G-1910%3A Avoid using the NOSONAR marker.::NOSONAR marker.
::warning file=examples/Core-G-1910.sql,line=6,col=4,endLine=6,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-1920.sql,line=5,col=8,endLine=5,endColumn=9,title=Core G-1920%3A Avoid syntax errors.::no viable alternative at input 'with\npro as (select 42)\nselect *'
::warning file=examples/Core-G-2110.sql,line=5,col=20,endLine=5,endColumn=37,title=Core G-2110%3A Try to use anchored declarations for variables%2C constants and types.::Hard-coded data type of l_last_name.
::warning file=examples/Core-G-2120.sql,line=5,col=15,endLine=5,endColumn=30,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined subtype big_string_type.
::warning file=examples/Core-G-2130.sql,line=5,col=14,endLine=5,endColumn=33,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_note.
::warning file=examples/Core-G-2135.sql,line=15,col=7,endLine=15,endColumn=16,title=Core G-2135%3A Avoid assigning values to local variables that are not used by a subsequent statement.::Value assigned to l_message is never used.
::warning file=examples/Core-G-2140.sql,line=4,col=11,endLine=4,endColumn=29,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_note.
::warning file=examples/Core-G-2140.sql,line=4,col=33,endLine=4,endColumn=37,title=Core G-2140%3A Never initialize variables with NULL.::l_note is unnecessarily initialised with NULL.
::warning file=examples/Core-G-2140.sql,line=6,col=4,endLine=6,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-2145.sql,line=10,col=7,endLine=10,endColumn=45,title=Core G-2145%3A Never self-assign a variable.::Self-assigned variable.
::error file=examples/Core-G-2150.sql,line=6,col=7,endLine=6,endColumn=21,title=Core G-2150%3A Avoid comparisons with NULL value%2C consider using IS [NOT] NULL.::Comparing l_value with NULL.
::warning file=examples/Core-G-2160.sql,line=6,col=7,endLine=6,endColumn=59,title=Core G-2160%3A Avoid initializing variables using functions in the declaration section.::Function call in declare section.
::warning file=examples/Core-G-2160.sql,line=8,col=4,endLine=8,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-2170.sql,line=10,col=10,endLine=10,endColumn=20,title=Core G-2170%3A Never overload variables.::Overloaded variable l_variable.
::warning file=examples/Core-G-2170.sql,line=12,col=10,endLine=12,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-2180.sql,line=4,col=4,endLine=4,endColumn=14,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable "sal+comm" does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-2180.sql,line=4,col=4,endLine=4,endColumn=14,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "sal+comm".
::warning file=examples/Core-G-2180.sql,line=5,col=4,endLine=5,endColumn=17,title=Core G-9114%3A Always follow naming conventions for constants.::Constant "my constant" does not match '(?i)^co_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-2180.sql,line=5,col=4,endLine=5,endColumn=17,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "my constant".
::warning file=examples/Core-G-2180.sql,line=6,col=4,endLine=6,endColumn=18,title=Core G-9113%3A Always follow naming conventions for exceptions.::Exception "my exception" does not match '(?i)^e_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-2180.sql,line=6,col=4,endLine=6,endColumn=18,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "my exception".
::warning file=examples/Core-G-2180.sql,line=8,col=4,endLine=8,endColumn=14,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "sal+comm".
::warning file=examples/Core-G-2180.sql,line=8,col=18,endLine=8,endColumn=31,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "my constant".
::warning file=examples/Core-G-2180.sql,line=9,col=17,endLine=9,endColumn=27,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "sal+comm".
::warning file=examples/Core-G-2180.sql,line=11,col=9,endLine=11,endColumn=23,title=Core G-2180%3A Never use quoted identifiers.::Quoted identifier "my exception".
::warning file=examples/Core-G-2185.sql,line=4,col=4,endLine=4,endColumn=5,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier i is less than 4 characters.
::warning file=examples/Core-G-2185.sql,line=5,col=4,endLine=5,endColumn=5,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier c is less than 4 characters.
::warning file=examples/Core-G-2185.sql,line=5,col=4,endLine=5,endColumn=5,title=Core G-9114%3A Always follow naming conventions for constants.::Constant c does not match '(?i)^co_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-2185.sql,line=6,col=4,endLine=6,endColumn=5,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier e is less than 4 characters.
::warning file=examples/Core-G-2185.sql,line=6,col=4,endLine=6,endColumn=5,title=Core G-9113%3A Always follow naming conventions for exceptions.::Exception e does not match '(?i)^e_[a-z0-9$#_]+$'.
::error file=examples/Core-G-2190.sql,line=9,col=11,endLine=9,endColumn=16,title=Core G-2190%3A Avoid using ROWID or UROWID.::Avoid using rowid.
::warning file=examples/Core-G-2210.sql,line=4,col=27,endLine=4,endColumn=33,title=Core G-2210%3A Avoid declaring NUMBER variables%2C constants or subtypes with no precision.::NUMBER declaration without precision.
::warning file=examples/Core-G-2220.sql,line=4,col=19,endLine=4,endColumn=30,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_result.
::warning file=examples/Core-G-2220.sql,line=4,col=19,endLine=4,endColumn=30,title=Core G-2220%3A Try to use PLS_INTEGER instead of NUMBER for arithmetic operations with integer values.::number(9,0) could be replaced by pls_integer.
::warning file=examples/Core-G-2220.sql,line=15,col=4,endLine=15,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-2230.sql,line=4,col=19,endLine=4,endColumn=30,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_result.
::warning file=examples/Core-G-2230.sql,line=4,col=19,endLine=4,endColumn=30,title=Core G-2230%3A Try to use SIMPLE_INTEGER datatype when appropriate.::number(9,0) could be replaced by simple_integer.
::warning file=examples/Core-G-2230.sql,line=14,col=4,endLine=14,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-2310.sql,line=5,col=32,endLine=5,endColumn=36,title=Core G-2310%3A Avoid using CHAR data type.::Use VARCHAR2 instead of CHAR data type.
::error file=examples/Core-G-2320.sql,line=4,col=32,endLine=4,endColumn=39,title=Core G-2320%3A Never use VARCHAR data type.::Use VARCHAR2 instead of CHAR data type.
::error file=examples/Core-G-2330.sql,line=8,col=14,endLine=8,endColumn=16,title=Core G-2330%3A Never use zero-length strings to substitute NULL.::Use NULL instead of zero-length string.
::error file=examples/Core-G-2340.sql,line=4,col=32,endLine=4,endColumn=45,title=Core G-2340%3A Always define your VARCHAR2 variables using CHAR SEMANTIC (if not defined anchored).::Missing character set length semantics.
::warning file=examples/Core-G-2410.sql,line=6,col=15,endLine=6,endColumn=26,title=Core G-2410%3A Try to use boolean data type for values with dual meaning.::Only values '0' and '1' assigned to l_bigger. Use BOOLEAN data type.
::warning file=examples/Core-G-2510.sql,line=4,col=11,endLine=4,endColumn=15,title=Core G-2510%3A Avoid using the LONG and LONG RAW data types.::Deprecated LONG data type used.
::warning file=examples/Core-G-2510.sql,line=5,col=11,endLine=5,endColumn=19,title=Core G-2510%3A Avoid using the LONG and LONG RAW data types.::Deprecated LONG RAW data type used.
::warning file=examples/Core-G-2610.sql,line=4,col=9,endLine=4,endColumn=31,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined weak ref cursor type local_weak_cursor_type. Consider using sys_refcursor instead.
::warning file=examples/Core-G-2610.sql,line=4,col=4,endLine=4,endColumn=46,title=Core G-2610%3A Never use self-defined weak ref cursor types.::Use sys_refcursor instead of self-defined weak ref cursor.
::error file=examples/Core-G-3110.sql,line=6,col=19,endLine=6,endColumn=30,title=Core G-3110%3A Always specify the target columns when coding an insert statement.::Missing target columns in insert statement.
::error file=examples/Core-G-3115.sql,line=4,col=8,endLine=4,endColumn=31,title=Core G-3115%3A Avoid self-assigning a column.::Self-assigned column first_name.
::error file=examples/Core-G-3120.sql,line=3,col=8,endLine=3,endColumn=17,title=Core G-3120%3A Always use table aliases when your SQL statement involves more than one source.::Missing table alias for last_name.
::error file=examples/Core-G-3120.sql,line=4,col=8,endLine=4,endColumn=18,title=Core G-3120%3A Always use table aliases when your SQL statement involves more than one source.::Missing table alias for first_name.
::error file=examples/Core-G-3120.sql,line=5,col=8,endLine=5,endColumn=23,title=Core G-3120%3A Always use table aliases when your SQL statement involves more than one source.::Missing table alias for department_name.
::warning file=examples/Core-G-3130.sql,line=7,col=3,endLine=8,endColumn=21,title=Core G-3130%3A Try to use ANSI SQL-92 join syntax.::Use ANSI SQL-92 instead of Oracle join syntax.
::warning file=examples/Core-G-3140.sql,line=12,col=22,endLine=12,endColumn=65,title=Core G-3140%3A Try to use anchored records as targets for your cursors.::Use anchored record as target for cursor c_employees.
::warning file=examples/Core-G-3140.sql,line=17,col=25,endLine=17,endColumn=68,title=Core G-3140%3A Try to use anchored records as targets for your cursors.::Use anchored record as target for cursor c_employees.
::error file=examples/Core-G-3145.sql,line=6,col=14,endLine=6,endColumn=15,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-3150.sql,line=18,col=37,endLine=18,endColumn=44,title=Core G-3150%3A Try to use identity columns for surrogate keys.::Missing identity column for surrogate key location_id.
::notice file=examples/Core-G-3150.sql,line=3,col=1,endLine=3,endColumn=7,title=Core G-1940%3A Avoid long checking times.::Checking time of 1.602 sec exceeded threshold of 1.500 sec.
::error file=examples/Core-G-3170.sql,line=5,col=39,endLine=5,endColumn=46,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for column_defaulted.
::warning file=examples/Core-G-3180.sql,line=8,col=11,endLine=8,endColumn=12,title=Core G-3180%3A Always specify column names instead of positional references in ORDER BY clauses.::Positional reference 4 in ORDER BY clause.
::warning file=examples/Core-G-3180.sql,line=8,col=13,endLine=8,endColumn=14,title=Core G-3180%3A Always specify column names instead of positional references in ORDER BY clauses.::Positional reference 1 in ORDER BY clause.
::warning file=examples/Core-G-3180.sql,line=8,col=15,endLine=8,endColumn=16,title=Core G-3180%3A Always specify column names instead of positional references in ORDER BY clauses.::Positional reference 3 in ORDER BY clause.
::error file=examples/Core-G-3182.sql,line=6,col=18,endLine=6,endColumn=19,title=Core G-3182%3A Always specify column names/aliases instead of positional references in GROUP BY clauses.::Positional reference in GROUP BY clause.
::warning file=examples/Core-G-3183.sql,line=6,col=11,endLine=6,endColumn=24,title=Core G-3183%3A Always specify column aliases instead of expressions in GROUP BY clauses.::Use column alias 'job' in GROUP BY clause.
::error file=examples/Core-G-3185.sql,line=7,col=8,endLine=7,endColumn=14,title=Core G-3185%3A Never use ROWNUM at the same query level as ORDER BY.::Using ROWNUM at the same query level as ORDER BY.
::error file=examples/Core-G-3185.sql,line=9,col=8,endLine=9,endColumn=14,title=Core G-3185%3A Never use ROWNUM at the same query level as ORDER BY.::Using ROWNUM at the same query level as ORDER BY.
::error file=examples/Core-G-3190.sql,line=7,col=1,endLine=7,endColumn=8,title=Core G-3190%3A Avoid using NATURAL JOIN.::Using NATURAL JOIN.
::error file=examples/Core-G-3195.sql,line=6,col=8,endLine=6,endColumn=32,title=Core G-3195%3A Always use wildcards in a LIKE clause.::Missing wildcards in LIKE clause.
::warning file=examples/Core-G-3210.sql,line=14,col=7,endLine=14,endColumn=13,title=Core G-3210%3A Always use BULK OPERATIONS (BULK COLLECT%2C FORALL) whenever you have to execute a DML statement for more than 4 times.::Row-by-row update statement.
::warning file=examples/Core-G-3220.sql,line=12,col=42,endLine=12,endColumn=57,title=Core G-3220%3A Always process saved exceptions from a FORALL statement.::Ignoring exceptions saved in forall statement.
::error file=examples/Core-G-3310.sql,line=24,col=10,endLine=24,endColumn=16,title=Core G-3310%3A Never commit within a cursor loop.::Committing in cursor loop.
::warning file=examples/Core-G-3310.sql,line=18,col=7,endLine=18,endColumn=13,title=Core G-3210%3A Always use BULK OPERATIONS (BULK COLLECT%2C FORALL) whenever you have to execute a DML statement for more than 4 times.::Row-by-row update statement.
::warning file=examples/Core-G-3320.sql,line=29,col=7,endLine=29,endColumn=13,title=Core G-3320%3A Try to move transactions within a non-cursor loop into procedures.::Missing procedure for transaction in non-cursor loop.
::warning file=examples/Core-G-3320.sql,line=13,col=7,endLine=13,endColumn=13,title=Core G-3210%3A Always use BULK OPERATIONS (BULK COLLECT%2C FORALL) whenever you have to execute a DML statement for more than 4 times.::Row-by-row insert statement.
::warning file=examples/Core-G-3320.sql,line=20,col=7,endLine=20,endColumn=13,title=Core G-3210%3A Always use BULK OPERATIONS (BULK COLLECT%2C FORALL) whenever you have to execute a DML statement for more than 4 times.::Row-by-row insert statement.
::error file=examples/Core-G-3330.sql,line=5,col=7,endLine=5,endColumn=36,title=Core G-3330%3A Avoid autonomous transactions.::Avoid autonomous transaction.
::error file=examples/Core-G-4110.sql,line=5,col=14,endLine=5,endColumn=15,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-4110.sql,line=22,col=10,endLine=22,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4110.sql,line=25,col=35,endLine=25,endColumn=56,title=Core G-4110%3A Always use %25NOTFOUND instead of NOT %25FOUND to check whether a cursor returned data.::Use %25NOTFOUND instead of NOT %25FOUND.
::error file=examples/Core-G-4120.sql,line=5,col=14,endLine=5,endColumn=15,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::error file=examples/Core-G-4120.sql,line=18,col=35,endLine=18,endColumn=55,title=Core G-4120%3A Avoid using %25NOTFOUND directly after the FETCH when working with BULK OPERATIONS and LIMIT clause.::Using %25NOTFOUND with LIMIT clause.
::warning file=examples/Core-G-4120.sql,line=23,col=10,endLine=23,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-4130.sql,line=13,col=12,endLine=13,endColumn=31,title=Core G-4130%3A Always close locally opened cursors.::Cursor c_department_salary is not closed.
::warning file=examples/Core-G-4140.sql,line=10,col=7,endLine=10,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-4140.sql,line=23,col=10,endLine=23,endColumn=22,title=Core G-4140%3A Avoid executing any statements between a SQL operation and the usage of an implicit cursor attribute.::Multiple statements executed before checking sql%25rowcount.
::warning file=examples/Core-G-4210.sql,line=6,col=4,endLine=6,endColumn=6,title=Core G-4210%3A Try to use CASE rather than an IF statement with multiple ELSIF paths.::Use CASE instead of IF.
::warning file=examples/Core-G-4220.sql,line=3,col=8,endLine=3,endColumn=14,title=Core G-4220%3A Try to use CASE rather than DECODE.::Use CASE instead of DECODE.
::warning file=examples/Core-G-4230.sql,line=3,col=8,endLine=3,endColumn=11,title=Core G-4230%3A Always use a COALESCE instead of a NVL command%2C if parameter 2 of the NVL function is a function call or a SELECT statement.::Use COALESCE instead of NVL.
::warning file=examples/Core-G-4240.sql,line=3,col=8,endLine=3,endColumn=12,title=Core G-4240%3A Always use a CASE instead of a NVL2 command if parameter 2 or 3 of NVL2 is either a function call or a SELECT statement.::Use CASE instead of NVL2.
::error file=examples/Core-G-4250.sql,line=11,col=12,endLine=11,endColumn=31,title=Core G-4250%3A Avoid using identical conditions in different branches of the same IF or CASE statement.::Condition already used in previous branch of CASE.
::warning file=examples/Core-G-4260.sql,line=6,col=7,endLine=6,endColumn=10,title=Core G-4260%3A Avoid inverting boolean conditions with NOT.::Inverting boolean condition.
::warning file=examples/Core-G-4270.sql,line=8,col=7,endLine=8,endColumn=24,title=Core G-4270%3A Avoid comparing boolean values to boolean literals.::Comparing boolean values to boolean literals.
::warning file=examples/Core-G-4310.sql,line=6,col=31,endLine=6,endColumn=48,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for co_digitarray.
::warning file=examples/Core-G-4310.sql,line=9,col=31,endLine=9,endColumn=49,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for co_errmsg.
::warning file=examples/Core-G-4310.sql,line=25,col=16,endLine=25,endColumn=20,title=Core G-4310%3A Never use GOTO statements in your code.::Using GOTO.
::warning file=examples/Core-G-4320.sql,line=7,col=4,endLine=7,endColumn=9,title=Core G-4320%3A Always label your loops.::Missing start label in while loop statement.
::warning file=examples/Core-G-4320.sql,line=10,col=8,endLine=10,endColumn=12,title=Core G-4320%3A Always label your loops.::Missing end label in while loop statement.
::warning file=examples/Core-G-4320.sql,line=12,col=4,endLine=12,endColumn=8,title=Core G-4320%3A Always label your loops.::Missing start label in basic loop statement.
::warning file=examples/Core-G-4320.sql,line=14,col=8,endLine=14,endColumn=12,title=Core G-4320%3A Always label your loops.::Missing end label in basic loop statement.
::warning file=examples/Core-G-4320.sql,line=13,col=7,endLine=13,endColumn=11,title=Core G-4380%3A Try to label your EXIT WHEN statements.::Missing label in EXIT statement.
::warning file=examples/Core-G-4320.sql,line=16,col=4,endLine=16,endColumn=7,title=Core G-4320%3A Always label your loops.::Missing start label in for loop statement.
::warning file=examples/Core-G-4320.sql,line=19,col=8,endLine=19,endColumn=12,title=Core G-4320%3A Always label your loops.::Missing end label in for loop statement.
::warning file=examples/Core-G-4320.sql,line=16,col=16,endLine=16,endColumn=18,title=Core G-4395%3A Avoid hard-coded upper or lower bound values with FOR loops.::Hard-coded upper bound value 10 in FOR loop.
::warning file=examples/Core-G-4320.sql,line=18,col=7,endLine=18,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4320.sql,line=21,col=4,endLine=21,endColumn=7,title=Core G-4320%3A Always label your loops.::Missing start label in cursor for loop statement.
::warning file=examples/Core-G-4320.sql,line=24,col=8,endLine=24,endColumn=12,title=Core G-4320%3A Always label your loops.::Missing end label in cursor for loop statement.
::warning file=examples/Core-G-4320.sql,line=23,col=7,endLine=23,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4325.sql,line=8,col=4,endLine=8,endColumn=16,title=Core G-4325%3A Never reuse labels in inner scope.::Reusing label my_label in inner scopes.
::warning file=examples/Core-G-4325.sql,line=11,col=7,endLine=11,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4330.sql,line=12,col=4,endLine=12,endColumn=8,title=Core G-4330%3A Always use a CURSOR FOR loop to process the complete cursor results unless you are using bulk operations.::Basic loop to process complete result set of cursor c_employees.
::warning file=examples/Core-G-4330.sql,line=15,col=7,endLine=15,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4340.sql,line=4,col=9,endLine=4,endColumn=24,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_employee_type.
::warning file=examples/Core-G-4340.sql,line=16,col=4,endLine=16,endColumn=8,title=Core G-4340%3A Always use a NUMERIC FOR loop to process a dense array.::Basic loop to process complete dense array t_employees.
::warning file=examples/Core-G-4340.sql,line=18,col=7,endLine=18,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4350.sql,line=4,col=9,endLine=4,endColumn=24,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_employee_type.
::error file=examples/Core-G-4350.sql,line=8,col=13,endLine=8,endColumn=52,title=Core G-4350%3A Always use 1 as lower and COUNT() as upper bound when looping through a dense array.::Always use 1 as lower and COUNT() as upper bound when looping through a dense array.
::warning file=examples/Core-G-4350.sql,line=10,col=7,endLine=10,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4360.sql,line=4,col=9,endLine=4,endColumn=24,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_employee_type.
::warning file=examples/Core-G-4360.sql,line=16,col=16,endLine=16,endColumn=38,title=Core G-4360%3A Always use a WHILE loop to process a loose array.::For loop to process sparse array t_employees.
::warning file=examples/Core-G-4360.sql,line=18,col=10,endLine=18,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4365.sql,line=8,col=7,endLine=8,endColumn=34,title=Core G-4365%3A Never use unconditional CONTINUE or EXIT in a loop.::Unconditional CONTINUE statement in loop.
::warning file=examples/Core-G-4370.sql,line=14,col=7,endLine=14,endColumn=11,title=Core G-4370%3A Avoid using EXIT to stop loop processing unless you are in a basic loop.::Using EXIT in while loop.
::warning file=examples/Core-G-4370.sql,line=26,col=7,endLine=26,endColumn=11,title=Core G-4370%3A Avoid using EXIT to stop loop processing unless you are in a basic loop.::Using EXIT in for loop.
::warning file=examples/Core-G-4370.sql,line=35,col=7,endLine=35,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4370.sql,line=37,col=7,endLine=37,endColumn=11,title=Core G-4370%3A Avoid using EXIT to stop loop processing unless you are in a basic loop.::Using EXIT in cursor for loop.
::warning file=examples/Core-G-4375.sql,line=11,col=10,endLine=11,endColumn=33,title=Core G-4365%3A Never use unconditional CONTINUE or EXIT in a loop.::Unconditional EXIT statement in loop.
::warning file=examples/Core-G-4375.sql,line=10,col=7,endLine=10,endColumn=9,title=Core G-4375%3A Always use EXIT WHEN instead of an IF statement to exit from a loop.::EXIT without condition in if statement.
::warning file=examples/Core-G-4380.sql,line=20,col=10,endLine=20,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4380.sql,line=25,col=10,endLine=25,endColumn=14,title=Core G-4380%3A Try to label your EXIT WHEN statements.::Missing label in EXIT statement.
::warning file=examples/Core-G-4380.sql,line=28,col=7,endLine=28,endColumn=11,title=Core G-4380%3A Try to label your EXIT WHEN statements.::Missing label in EXIT statement.
::warning file=examples/Core-G-4385.sql,line=10,col=4,endLine=10,endColumn=7,title=Core G-4385%3A Never use a cursor for loop to check whether a cursor returns data.::Cursor for loop checks only existence of data.
::error file=examples/Core-G-4387.sql,line=8,col=7,endLine=8,endColumn=10,title=Core G-4387%3A Never use a FOR LOOP for a query that should return not more than one row.::Never use a FOR LOOP for a query that should return not more than one row.
::warning file=examples/Core-G-4390.sql,line=16,col=8,endLine=16,endColumn=9,title=Core G-4390%3A Avoid use of unreferenced FOR loop indexes.::Unused FOR loop index i.
::warning file=examples/Core-G-4390.sql,line=18,col=7,endLine=18,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-4395.sql,line=5,col=13,endLine=5,endColumn=14,title=Core G-4395%3A Avoid hard-coded upper or lower bound values with FOR loops.::Hard-coded lower bound value 2 in FOR loop.
::warning file=examples/Core-G-4395.sql,line=5,col=16,endLine=5,endColumn=17,title=Core G-4395%3A Avoid hard-coded upper or lower bound values with FOR loops.::Hard-coded upper bound value 5 in FOR loop.
::warning file=examples/Core-G-4395.sql,line=7,col=7,endLine=7,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-5010.sql,line=7,col=4,endLine=7,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-5010.sql,line=9,col=4,endLine=9,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-5020.sql,line=11,col=10,endLine=11,endColumn=17,title=Core G-5020%3A Never handle unnamed exceptions using the error number.::Never handle unnamed exceptions using the error number.
::error file=examples/Core-G-5030.sql,line=5,col=4,endLine=5,endColumn=17,title=Core G-5030%3A Never assign predefined exception names to user defined exceptions.::Using predefined exception name no_data_found as user defined exception.
::warning file=examples/Core-G-5030.sql,line=5,col=4,endLine=5,endColumn=17,title=Core G-9113%3A Always follow naming conventions for exceptions.::Exception no_data_found does not match '(?i)^e_[a-z0-9$#_]+$'.
::error file=examples/Core-G-5030.sql,line=15,col=13,endLine=15,endColumn=26,title=Core G-5070%3A Avoid using Oracle predefined exceptions.::Raising Oracle predefined exception no_data_found.
::warning file=examples/Core-G-5030.sql,line=19,col=7,endLine=19,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-5040.sql,line=6,col=9,endLine=6,endColumn=15,title=Core G-5040%3A Avoid use of WHEN OTHERS clause in an exception section without any other specific handlers.::Using WHEN OTHERS without any other specific handlers.
::warning file=examples/Core-G-5050.sql,line=6,col=28,endLine=6,endColumn=34,title=Core G-5050%3A Avoid use of the RAISE_APPLICATION_ERROR built-in procedure with a hard-coded 20nnn error number or hard-coded message.::Using RAISE_APPLICATION_ERROR with a hard-coded -20501 error number.
::warning file=examples/Core-G-5060.sql,line=4,col=13,endLine=4,endColumn=23,title=Core G-7460%3A Try to define your packaged/standalone function deterministic if appropriate.::Define function name_by_id as deterministic if appropriate.
::warning file=examples/Core-G-5060.sql,line=10,col=9,endLine=10,endColumn=13,title=Core G-5060%3A Avoid unhandled exceptions.::Unhandled NO_DATA_FOUND and TOO_MANY_ROWS exception.
::error file=examples/Core-G-5070.sql,line=4,col=10,endLine=4,endColumn=23,title=Core G-5070%3A Avoid using Oracle predefined exceptions.::Raising Oracle predefined exception no_data_found.
::warning file=examples/Core-G-5080.sql,line=20,col=49,endLine=20,endColumn=56,title=Core G-5080%3A Always use FORMAT_ERROR_BACKTRACE when using FORMAT_ERROR_STACK or SQLERRM.::Missing FORMAT_ERROR_BACKTRACE call.
::warning file=examples/Core-G-6010.sql,line=6,col=22,endLine=6,endColumn=62,title=Core G-6010%3A Always use a character variable to execute dynamic SQL.::Use a variable instead of a literal to execute dynamic SQL.
::warning file=examples/Core-G-6020.sql,line=18,col=47,endLine=18,endColumn=65,title=Core G-6020%3A Try to use output bind arguments in the RETURNING INTO clause of dynamic DML statements rather than the USING clause.::Use RETURNING INTO clause for out_new_salary.
::warning file=examples/Core-G-7110.sql,line=7,col=32,endLine=7,endColumn=42,title=Core G-7110%3A Try to use named notation when calling program units.::Use named notation.
::warning file=examples/Core-G-7110.sql,line=7,col=43,endLine=7,endColumn=48,title=Core G-7110%3A Try to use named notation when calling program units.::Use named notation.
::warning file=examples/Core-G-7120.sql,line=21,col=1,endLine=21,endColumn=4,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of package body employee_api.
::warning file=examples/Core-G-7120.sql,line=20,col=4,endLine=20,endColumn=7,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of function employee_by_id.
::warning file=examples/Core-G-7125.sql,line=3,col=1,endLine=3,endColumn=7,title=Core G-7125%3A Always use CREATE OR REPLACE instead of CREATE alone.::Missing OR REPLACE in create statement.
::warning file=examples/Core-G-7130.sql,line=11,col=13,endLine=11,endColumn=18,title=Core G-7130%3A Always use parameters or pull in definitions rather than referencing external variables in a local program unit.::Using external variable r_emp.
::warning file=examples/Core-G-7130.sql,line=12,col=29,endLine=12,endColumn=34,title=Core G-7130%3A Always use parameters or pull in definitions rather than referencing external variables in a local program unit.::Using external variable r_emp.
::warning file=examples/Core-G-7130.sql,line=12,col=44,endLine=12,endColumn=49,title=Core G-7130%3A Always use parameters or pull in definitions rather than referencing external variables in a local program unit.::Using external variable r_emp.
::warning file=examples/Core-G-7130.sql,line=23,col=7,endLine=23,endColumn=31,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-7140.sql,line=5,col=16,endLine=5,endColumn=23,title=Core G-7140%3A Always ensure that locally defined procedures or functions are referenced.::Unused function my_func.
::warning file=examples/Core-G-7150.sql,line=6,col=7,endLine=6,endColumn=17,title=Core G-7150%3A Try to remove unused parameters.::Unused parameter in_manager.
::warning file=examples/Core-G-7160.sql,line=5,col=20,endLine=5,endColumn=33,title=Core G-7160%3A Always explicitly state parameter mode.::Explicitly state parameter mode of in_first_name.
::warning file=examples/Core-G-7160.sql,line=6,col=20,endLine=6,endColumn=32,title=Core G-7160%3A Always explicitly state parameter mode.::Explicitly state parameter mode of in_last_name.
::warning file=examples/Core-G-7160.sql,line=7,col=20,endLine=7,endColumn=28,title=Core G-7160%3A Always explicitly state parameter mode.::Explicitly state parameter mode of in_email.
::warning file=examples/Core-G-7160.sql,line=8,col=20,endLine=8,endColumn=36,title=Core G-7160%3A Always explicitly state parameter mode.::Explicitly state parameter mode of in_department_id.
::warning file=examples/Core-G-7170.sql,line=7,col=7,endLine=7,endColumn=55,title=Core G-7170%3A Avoid using an IN OUT parameter as IN or OUT only.::io_employee_id is used as IN only.
::warning file=examples/Core-G-7170.sql,line=8,col=7,endLine=8,endColumn=50,title=Core G-7170%3A Avoid using an IN OUT parameter as IN or OUT only.::io_salary is used as OUT only.
::error file=examples/Core-G-7170.sql,line=7,col=7,endLine=7,endColumn=21,title=Core G-7330%3A Always assign values to OUT parameters.::No value assigned to OUT parameter io_employee_id.
::warning file=examples/Core-G-7170.sql,line=22,col=4,endLine=22,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-7180.sql,line=12,col=45,endLine=12,endColumn=49,title=Core G-1050%3A Avoid using literals in your code.::Literal 9000 is used 4 times.
::warning file=examples/Core-G-7180.sql,line=13,col=45,endLine=13,endColumn=50,title=Core G-1050%3A Avoid using literals in your code.::Literal 16000 is used 2 times.
::warning file=examples/Core-G-7180.sql,line=21,col=45,endLine=21,endColumn=50,title=Core G-1050%3A Avoid using literals in your code.::Literal 15000 is used 2 times.
::warning file=examples/Core-G-7180.sql,line=24,col=45,endLine=24,endColumn=49,title=Core G-1050%3A Avoid using literals in your code.::Literal 5500 is used 2 times.
::warning file=examples/Core-G-7180.sql,line=8,col=24,endLine=8,endColumn=33,title=Core G-8310%3A Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.::Input size of parameter in_job_id not validated.
::warning file=examples/Core-G-7180.sql,line=10,col=4,endLine=10,endColumn=9,title=Core G-7180%3A Try to keep the complexity of functions%2C procedures and triggers simple.::job_util.max_salary has a cyclomatic complexity of 20.
::warning file=examples/Core-G-7220.sql,line=9,col=13,endLine=9,endColumn=23,title=Core G-7220%3A Always use forward declaration for private functions and procedures.::Missing forward declaration for private function does_exist.
::warning file=examples/Core-G-7220.sql,line=4,col=14,endLine=4,endColumn=17,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier del is less than 4 characters.
::warning file=examples/Core-G-7220.sql,line=9,col=13,endLine=9,endColumn=23,title=Core G-7460%3A Try to define your packaged/standalone function deterministic if appropriate.::Define function does_exist as deterministic if appropriate.
::warning file=examples/Core-G-7220.sql,line=28,col=14,endLine=28,endColumn=17,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier del is less than 4 characters.
::warning file=examples/Core-G-7230.sql,line=6,col=4,endLine=6,endColumn=21,title=Core G-7230%3A Avoid declaring global variables public.::Global variable g_salary_increase is public.
::warning file=examples/Core-G-7250.sql,line=21,col=4,endLine=21,endColumn=11,title=Core G-7250%3A Never use RETURN in package initialization block.::RETURN statement in package initialization block.
::warning file=examples/Core-G-7250.sql,line=21,col=4,endLine=21,endColumn=11,title=Core G-1040%3A Avoid dead code.::Dead code.
::warning file=examples/Core-G-7310.sql,line=3,col=29,endLine=3,endColumn=41,title=Core G-7310%3A Avoid standalone procedures – put your procedures in packages.::Put my_procedure in a package.
::warning file=examples/Core-G-7320.sql,line=11,col=13,endLine=11,endColumn=20,title=Core G-7320%3A Avoid using RETURN statements in a PROCEDURE.::RETURN statement in procedure my_procedure.
::warning file=examples/Core-G-7330.sql,line=12,col=7,endLine=12,endColumn=16,title=Core G-2135%3A Avoid assigning values to local variables that are not used by a subsequent statement.::Value assigned to l_message is never used.
::warning file=examples/Core-G-7330.sql,line=6,col=7,endLine=6,endColumn=19,title=Core G-7150%3A Try to remove unused parameters.::Unused parameter out_greeting.
::error file=examples/Core-G-7330.sql,line=6,col=7,endLine=6,endColumn=19,title=Core G-7330%3A Always assign values to OUT parameters.::No value assigned to OUT parameter out_greeting.
::warning file=examples/Core-G-7410.sql,line=3,col=28,endLine=3,endColumn=39,title=Core G-7410%3A Avoid standalone functions – put your functions in packages.::Put my_function in a package.
::warning file=examples/Core-G-7420.sql,line=18,col=13,endLine=18,endColumn=19,title=Core G-7420%3A Always make the RETURN statement the last statement of your function.::RETURN is not the last statement in my_function.
::warning file=examples/Core-G-7430.sql,line=12,col=10,endLine=12,endColumn=16,title=Core G-7420%3A Always make the RETURN statement the last statement of your function.::RETURN is not the last statement in my_function.
::warning file=examples/Core-G-7430.sql,line=10,col=10,endLine=10,endColumn=16,title=Core G-7430%3A Try to use no more than one RETURN statement within a function.::RETURN used 2 times in my_function.
::warning file=examples/Core-G-7440.sql,line=4,col=25,endLine=4,endColumn=42,title=Core G-7440%3A Never use OUT parameters to return values from a function.::OUT parameter out_date in my_function.
::error file=examples/Core-G-7450.sql,line=8,col=14,endLine=8,endColumn=18,title=Core G-7450%3A Never return a NULL value from a BOOLEAN function.::Returning NULL in BOOLEAN function my_function.
::warning file=examples/Core-G-7460.sql,line=4,col=13,endLine=4,endColumn=23,title=Core G-7460%3A Try to define your packaged/standalone function deterministic if appropriate.::Define function name_by_id as deterministic if appropriate.
::warning file=examples/Core-G-7510.sql,line=4,col=28,endLine=4,endColumn=45,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for co_hello_world.
::warning file=examples/Core-G-7510.sql,line=6,col=4,endLine=6,endColumn=24,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-7510.sql,line=6,col=4,endLine=6,endColumn=15,title=Core G-7510%3A Always prefix Oracle supplied packages with owner schema name.::Prefix Oracle supplied package dbms_output with owner schema name.
::error file=examples/Core-G-7515.sql,line=4,col=12,endLine=4,endColumn=24,title=Core G-7515%3A Always prefix Oracle supplied object types with owner schema name.::Prefix Oracle supplied object type json_array_t with owner schema name.
::error file=examples/Core-G-7515.sql,line=6,col=15,endLine=6,endColumn=27,title=Core G-7515%3A Always prefix Oracle supplied object types with owner schema name.::Prefix Oracle supplied object type json_array_t with owner schema name.
::warning file=examples/Core-G-7515.sql,line=7,col=4,endLine=7,endColumn=28,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::warning file=examples/Core-G-7520.sql,line=4,col=4,endLine=4,endColumn=23,title=Core G-7520%3A Avoid using deprecated units in your own code.::sys.dbms_lock.sleep is deprecated.
::warning file=examples/Core-G-7710.sql,line=6,col=16,endLine=6,endColumn=32,title=Core G-7710%3A Avoid cascading triggers.::Cascading trigger on departments_hist via dept_hist_br_i.
::warning file=examples/Core-G-7720.sql,line=4,col=35,endLine=4,endColumn=60,title=Core G-7730%3A Avoid multiple DML events per trigger.::Multiple DML events in trigger dept_br_u.
::error file=examples/Core-G-7720.sql,line=4,col=8,endLine=4,endColumn=31,title=Core G-7720%3A Never use multiple UPDATE OF in trigger event clause.::Multiple UPDATE OF in trigger dept_br_u.
::warning file=examples/Core-G-7730.sql,line=4,col=18,endLine=4,endColumn=24,title=Core G-7730%3A Avoid multiple DML events per trigger.::Multiple DML events in trigger dept_br_iu.
::warning file=examples/Core-G-7740.sql,line=8,col=44,endLine=8,endColumn=51,title=Core G-3150%3A Try to use identity columns for surrogate keys.::Missing identity column for surrogate key department_id.
::warning file=examples/Core-G-7740.sql,line=4,col=18,endLine=4,endColumn=24,title=Core G-7730%3A Avoid multiple DML events per trigger.::Multiple DML events in trigger dept_br_iu.
::warning file=examples/Core-G-7810.sql,line=6,col=25,endLine=6,endColumn=32,title=Core G-7810%3A Never use SQL inside PL/SQL to read sequence numbers (or SYSDATE).::SQL used to access sequence employees_seq within PL/SQL.
::error file=examples/Core-G-7910.sql,line=7,col=7,endLine=8,endColumn=59,title=Core G-7910%3A Never use DML within a SQL macro.::Insert used in SQL macro row_generator.
::error file=examples/Core-G-7910.sql,line=9,col=7,endLine=9,endColumn=14,title=Core G-7910%3A Never use DML within a SQL macro.::Commit used in SQL macro row_generator.
::warning file=examples/Core-G-7910.sql,line=4,col=27,endLine=4,endColumn=38,title=Core G-8310%3A Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.::Input size of parameter in_num_rows not validated.
::warning file=examples/Core-G-8110.sql,line=8,col=11,endLine=8,endColumn=19,title=Core G-8110%3A Never use SELECT COUNT(*) if you are only interested in the existence of a row.::SELECT COUNT(*) used to check the existence of a row.
::warning file=examples/Core-G-8120.sql,line=4,col=14,endLine=4,endColumn=17,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier ins is less than 4 characters.
::warning file=examples/Core-G-8120.sql,line=7,col=14,endLine=7,endColumn=22,title=Core G-8110%3A Never use SELECT COUNT(*) if you are only interested in the existence of a row.::SELECT COUNT(*) used to check the existence of a row.
::warning file=examples/Core-G-8120.sql,line=12,col=10,endLine=12,endColumn=21,title=Core G-8120%3A Never check existence of a row to decide whether to create it or not.::Checking existence of a row before insert into departments.
::warning file=examples/Core-G-8210.sql,line=9,col=11,endLine=9,endColumn=13,title=Core G-8210%3A Always use synonyms when accessing objects of another application schema.::Using schema prefix oe.
::warning file=examples/Core-G-8310.sql,line=24,col=13,endLine=24,endColumn=19,title=Core G-7420%3A Always make the RETURN statement the last statement of your function.::RETURN is not the last statement in dept_by_name.
::warning file=examples/Core-G-8310.sql,line=21,col=10,endLine=21,endColumn=16,title=Core G-7430%3A Try to use no more than one RETURN statement within a function.::RETURN used 2 times in dept_by_name.
::warning file=examples/Core-G-8310.sql,line=5,col=7,endLine=5,endColumn=19,title=Core G-8310%3A Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.::Input size of parameter in_dept_name not validated.
::error file=examples/Core-G-8410.sql,line=14,col=19,endLine=14,endColumn=28,title=Core G-8410%3A Always use application locks to ensure a program unit is only running once at a given time.::Acquiring application lock via insert statement.
::error file=examples/Core-G-8410.sql,line=20,col=19,endLine=20,endColumn=28,title=Core G-8410%3A Always use application locks to ensure a program unit is only running once at a given time.::Releasing application lock via delete statement.
::warning file=examples/Core-G-8510.sql,line=14,col=10,endLine=14,endColumn=34,title=Core G-5010%3A Try to use a error/logging framework for your application.::Use a logging framework instead of DBMS_OUTPUT.
::error file=examples/Core-G-9010.sql,line=12,col=30,endLine=12,endColumn=37,title=Core G-9010%3A Always use a format model in string to date/time conversion functions.::Missing format model in to_date call.
::warning file=examples/Core-G-9020.sql,line=12,col=23,endLine=12,endColumn=32,title=Core G-9020%3A Try to use a format model and NLS_NUMERIC_CHARACTERS in string to number conversion functions.::Missing format model and NLS_NUMERIC_CHARACTERS in to_number call.
::warning file=examples/Core-G-9030.sql,line=12,col=30,endLine=12,endColumn=37,title=Core G-9030%3A Try to define a default value on conversion errors.::Missing conversion error handler in to_date call.
::error file=examples/Core-G-9040.sql,line=14,col=17,endLine=14,endColumn=29,title=Core G-9040%3A Try using FX in string to date/time conversion format model to avoid fuzzy conversion.::Missing FX in format model of to_date call.
::warning file=examples/Core-G-9101.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-9101%3A Always follow naming conventions for global variables.::Global variable some_name does not match '(?i)^g_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9101.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable some_name.
::warning file=examples/Core-G-9102.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable some_name.
::warning file=examples/Core-G-9102.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable some_name does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9103.sql,line=4,col=4,endLine=4,endColumn=10,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable l_dept.
::warning file=examples/Core-G-9103.sql,line=4,col=4,endLine=4,endColumn=10,title=Core G-9103%3A Always follow naming conventions for cursor variables.::Cursor variable l_dept does not match '(?i)^c_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9104.sql,line=4,col=4,endLine=4,endColumn=7,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier emp is less than 4 characters.
::warning file=examples/Core-G-9104.sql,line=4,col=4,endLine=4,endColumn=7,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable emp does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9104.sql,line=4,col=4,endLine=4,endColumn=7,title=Core G-9104%3A Always follow naming conventions for record variables.::Record variable emp does not match '(?i)^r_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9104.sql,line=5,col=9,endLine=5,endColumn=20,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined record type r_dept_type.
::warning file=examples/Core-G-9104.sql,line=10,col=4,endLine=10,endColumn=8,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable dept.
::warning file=examples/Core-G-9104.sql,line=10,col=4,endLine=10,endColumn=8,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable dept does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9104.sql,line=10,col=4,endLine=10,endColumn=8,title=Core G-9104%3A Always follow naming conventions for record variables.::Record variable dept does not match '(?i)^r_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9105.sql,line=4,col=9,endLine=4,endColumn=22,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_varray_type.
::warning file=examples/Core-G-9105.sql,line=5,col=4,endLine=5,endColumn=10,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable array1.
::warning file=examples/Core-G-9105.sql,line=5,col=4,endLine=5,endColumn=10,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable array1 does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9105.sql,line=5,col=4,endLine=5,endColumn=10,title=Core G-9105%3A Always follow naming conventions for collection variables (arrays/tables).::Collection variable array1 does not match '(?i)^t_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9105.sql,line=6,col=9,endLine=6,endColumn=28,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_nested_table_type.
::warning file=examples/Core-G-9105.sql,line=7,col=4,endLine=7,endColumn=10,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable array2.
::warning file=examples/Core-G-9105.sql,line=7,col=4,endLine=7,endColumn=10,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable array2 does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9105.sql,line=7,col=4,endLine=7,endColumn=10,title=Core G-9105%3A Always follow naming conventions for collection variables (arrays/tables).::Collection variable array2 does not match '(?i)^t_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9105.sql,line=8,col=9,endLine=8,endColumn=27,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_assoc_array_type.
::warning file=examples/Core-G-9105.sql,line=9,col=4,endLine=9,endColumn=10,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable array3.
::warning file=examples/Core-G-9105.sql,line=9,col=4,endLine=9,endColumn=10,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable array3 does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9105.sql,line=9,col=4,endLine=9,endColumn=10,title=Core G-9105%3A Always follow naming conventions for collection variables (arrays/tables).::Collection variable array3 does not match '(?i)^t_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9106.sql,line=3,col=24,endLine=3,endColumn=33,title=Core G-9217%3A Always follow naming conventions for object types.::Object type dept_type does not match '(?i)^[a-z][a-z0-9$#_]*_ot$'.
::warning file=examples/Core-G-9106.sql,line=11,col=4,endLine=11,endColumn=8,title=Core G-1030%3A Avoid defining variables that are not used.::Unused variable dept.
::warning file=examples/Core-G-9106.sql,line=11,col=4,endLine=11,endColumn=8,title=Core G-9102%3A Always follow naming conventions for local variables.::Local variable dept does not match '(?i)^((l_[a-z0-9$#_]+)|[ijk])$'.
::warning file=examples/Core-G-9106.sql,line=11,col=4,endLine=11,endColumn=8,title=Core G-9106%3A Always follow naming conventions for object variables.::Object variable dept does not match '(?i)^o_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9107.sql,line=4,col=17,endLine=4,endColumn=25,title=Core G-9107%3A Always follow naming conventions for cursor parameters.::Cursor parameter in_ename does not match '(?i)^p_[a-z0-9$#_]+$'.
::error file=examples/Core-G-9107.sql,line=5,col=14,endLine=5,endColumn=15,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-9108.sql,line=4,col=14,endLine=4,endColumn=16,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier p2 is less than 4 characters.
::warning file=examples/Core-G-9108.sql,line=4,col=17,endLine=4,endColumn=22,title=Core G-9108%3A Always follow naming conventions for IN parameters of functions and procedures.::IN parameter param does not match '(?i)^in_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9109.sql,line=4,col=14,endLine=4,endColumn=16,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier p2 is less than 4 characters.
::warning file=examples/Core-G-9109.sql,line=4,col=17,endLine=4,endColumn=22,title=Core G-9109%3A Always follow naming conventions for OUT parameters of functions and procedures.::OUT parameter param does not match '(?i)^out_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9110.sql,line=4,col=14,endLine=4,endColumn=16,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier p2 is less than 4 characters.
::warning file=examples/Core-G-9110.sql,line=4,col=17,endLine=4,endColumn=22,title=Core G-9110%3A Always follow naming conventions for IN/OUT parameters of functions and procedures.::IN/OUT parameter param does not match '(?i)^io_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9111.sql,line=4,col=9,endLine=4,endColumn=17,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined record type dept_typ.
::warning file=examples/Core-G-9111.sql,line=4,col=9,endLine=4,endColumn=17,title=Core G-9111%3A Always follow naming conventions for record type definitions.::Record type definition dept_typ does not match '(?i)^r_[a-z0-9$#_]+_type$'.
::warning file=examples/Core-G-9112.sql,line=4,col=9,endLine=4,endColumn=17,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type t_varray.
::warning file=examples/Core-G-9112.sql,line=4,col=9,endLine=4,endColumn=17,title=Core G-9112%3A Always follow naming conventions for collection type definitions (arrays/tables).::Collection type definition t_varray does not match '(?i)^t_[a-z0-9$#_]+_type$'.
::warning file=examples/Core-G-9112.sql,line=5,col=9,endLine=5,endColumn=26,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type nested_table_type.
::warning file=examples/Core-G-9112.sql,line=5,col=9,endLine=5,endColumn=26,title=Core G-9112%3A Always follow naming conventions for collection type definitions (arrays/tables).::Collection type definition nested_table_type does not match '(?i)^t_[a-z0-9$#_]+_type$'.
::warning file=examples/Core-G-9112.sql,line=6,col=9,endLine=6,endColumn=24,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined collection type x_assoc_array_y.
::warning file=examples/Core-G-9112.sql,line=6,col=9,endLine=6,endColumn=24,title=Core G-9112%3A Always follow naming conventions for collection type definitions (arrays/tables).::Collection type definition x_assoc_array_y does not match '(?i)^t_[a-z0-9$#_]+_type$'.
::warning file=examples/Core-G-9113.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-1030%3A Avoid defining variables that are not used.::Unused exception some_name.
::warning file=examples/Core-G-9113.sql,line=4,col=4,endLine=4,endColumn=13,title=Core G-9113%3A Always follow naming conventions for exceptions.::Exception some_name does not match '(?i)^e_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9114.sql,line=4,col=4,endLine=4,endColumn=11,title=Core G-1030%3A Avoid defining variables that are not used.::Unused constant maximum.
::warning file=examples/Core-G-9114.sql,line=4,col=4,endLine=4,endColumn=11,title=Core G-9114%3A Always follow naming conventions for constants.::Constant maximum does not match '(?i)^co_[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9115.sql,line=4,col=12,endLine=4,endColumn=22,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined subtype short_text.
::warning file=examples/Core-G-9115.sql,line=4,col=12,endLine=4,endColumn=22,title=Core G-9115%3A Always follow naming conventions for subtypes.::Subtype short_text does not match '(?i)^[a-z][a-z0-9$#_]*_type$'.
::warning file=examples/Core-G-9116.sql,line=4,col=9,endLine=4,endColumn=20,title=Core G-2120%3A Try to have a single location to define your types.::Locally defined record type r_dept_type.
::warning file=examples/Core-G-9116.sql,line=6,col=10,endLine=6,endColumn=31,title=Core G-9116%3A Always follow naming conventions for record fields.::Field numéro_de_département does not match '(?i)^[a-z0-9$#_]+$'.
::warning file=examples/Core-G-9201.sql,line=3,col=14,endLine=3,endColumn=26,title=Core G-9201%3A Always follow naming conventions for tables.::Table départements does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9202.sql,line=4,col=4,endLine=4,endColumn=25,title=Core G-9202%3A Always follow naming conventions for table/view columns.::Column numéro_de_département does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9204.sql,line=6,col=15,endLine=6,endColumn=30,title=Core G-9204%3A Always follow naming conventions for primary key constraints.::Primary key emp#primary#key does not match '(?i)^[a-z][a-z0-9$#_]*_pk$'.
::warning file=examples/Core-G-9205.sql,line=7,col=15,endLine=7,endColumn=20,title=Core G-9205%3A Always follow naming conventions for unique constraints.::Unique constraint ename does not match '(?i)^[a-z][a-z0-9$#_]*_uk\d*$'.
::error file=examples/Core-G-9206.sql,line=4,col=22,endLine=4,endColumn=29,title=Core G-3170%3A Always use DEFAULT ON NULL declarations to assign default values to table columns if you refuse to store NULL values.::Missing DEFAULT ON NULL for parent_id.
::warning file=examples/Core-G-9206.sql,line=12,col=15,endLine=12,endColumn=27,title=Core G-9206%3A Always follow naming conventions for foreign key constraints.::Foreign key child_parent does not match '(?i)^[a-z][a-z0-9$#_]*_fk\d*$'.
::warning file=examples/Core-G-9207.sql,line=6,col=15,endLine=6,endColumn=22,title=Core G-9207%3A Always follow naming conventions for check constraints.::Check constraint emp_sal does not match '(?i)^[a-z][a-z0-9$#_]*_ck$'.
::error file=examples/Core-G-9208.sql,line=12,col=4,endLine=12,endColumn=5,title=Core G-1920%3A Avoid syntax errors.::mismatched input ')' expecting {<EOF>, '\', ';', '/', PSQL_EXEC}
::warning file=examples/Core-G-9209.sql,line=3,col=31,endLine=3,endColumn=46,title=Core G-9209%3A Always follow naming conventions for global temporary tables.::Global temporary table département_tmp does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9210.sql,line=3,col=24,endLine=3,endColumn=49,title=Core G-9210%3A Always follow naming conventions for views.::View salaires_des_départements does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9213.sql,line=3,col=27,endLine=3,endColumn=32,title=Core G-9213%3A Always follow naming conventions for triggers.::Trigger logon does not match '(?i)^[a-z][a-z0-9$#_]*_(trg|((b|a)r?|io)_i?u?d?)$'.
::warning file=examples/Core-G-9214.sql,line=5,col=1,endLine=5,endColumn=4,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of package département_api.
::warning file=examples/Core-G-9214.sql,line=3,col=27,endLine=3,endColumn=42,title=Core G-9214%3A Always follow naming conventions for PL/SQL packages.::Package département_api does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9215.sql,line=6,col=1,endLine=6,endColumn=4,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of package departement_api.
::warning file=examples/Core-G-9215.sql,line=5,col=13,endLine=5,endColumn=35,title=Core G-7460%3A Try to define your packaged/standalone function deterministic if appropriate.::Define function département_id_par_nom as deterministic if appropriate.
::warning file=examples/Core-G-9215.sql,line=5,col=13,endLine=5,endColumn=35,title=Core G-9215%3A Always follow naming conventions for functions.::Function département_id_par_nom does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9216.sql,line=6,col=1,endLine=6,endColumn=4,title=Core G-7120%3A Always add the name of the program unit to its end keyword.::Missing end label of package department_api.
::warning file=examples/Core-G-9216.sql,line=5,col=14,endLine=5,endColumn=32,title=Core G-9216%3A Always follow naming conventions for procedures.::Procedure fermer_département does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9217.sql,line=3,col=24,endLine=3,endColumn=28,title=Core G-9217%3A Always follow naming conventions for object types.::Object type dept does not match '(?i)^[a-z][a-z0-9$#_]*_ot$'.
::warning file=examples/Core-G-9218.sql,line=4,col=4,endLine=4,endColumn=18,title=Core G-9218%3A Always follow naming conventions for object type attributes.::Attribute département_id does not match '(?i)^[a-z][a-z0-9$#_]*$'.
::warning file=examples/Core-G-9219.sql,line=9,col=24,endLine=9,endColumn=29,title=Core G-9219%3A Always follow naming conventions for collection types.::Collection type depts does not match '(?i)^[a-z][a-z0-9$#_]*_ct$'.
::warning file=examples/Core-G-9501.sql,line=5,col=31,endLine=5,endColumn=50,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for co_templ.
::warning file=examples/Core-G-9501.sql,line=6,col=22,endLine=6,endColumn=40,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_table_name.
::warning file=examples/Core-G-9501.sql,line=7,col=22,endLine=7,endColumn=41,title=Core G-2130%3A Try to use subtypes for constructs used often in your code.::Consider using a subtype for l_sql.
::warning file=examples/Core-G-9501.sql,line=4,col=14,endLine=4,endColumn=15,title=Core G-2185%3A Avoid using overly short names for explicitly or implicitly declared identifiers.::Identifier f is less than 4 characters.
::warning file=examples/Core-G-9501.sql,line=4,col=14,endLine=4,endColumn=15,title=Core G-7460%3A Try to define your packaged/standalone function deterministic if appropriate.::Define function f as deterministic if appropriate.
::warning file=examples/Core-G-9501.sql,line=4,col=17,endLine=4,endColumn=30,title=Core G-8310%3A Always validate input parameter size by assigning the parameter to a size limited variable in the declaration section of program unit.::Input size of parameter in_table_name not validated.
::error file=examples/Core-G-9501.sql,line=9,col=25,endLine=9,endColumn=38,title=Core G-9501%3A Never use parameter in string expression of dynamic SQL. Use asserted local variable instead.::SQL Injection possible via parameter in_table_name.
::warning file=examples/Core-G-9600.sql,line=6,col=8,endLine=6,endColumn=19,title=Core G-9600%3A Never define more than one comment with hints.::Unused hint. Only the first comment with hints is considered.
::warning file=examples/Core-G-9601.sql,line=3,col=12,endLine=3,endColumn=21,title=Core G-9601%3A Never use unknown hints.::Using unknown nologging hint.
::error file=examples/Core-G-9601.sql,line=4,col=8,endLine=4,endColumn=18,title=Core G-3110%3A Always specify the target columns when coding an insert statement.::Missing target columns in insert statement.
::error file=examples/Core-G-9601.sql,line=5,col=8,endLine=5,endColumn=9,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-9602.sql,line=3,col=20,endLine=3,endColumn=23,title=Core G-9602%3A Always use the alias name instead of the table name.::Use e instead of emp in leading hint.
::warning file=examples/Core-G-9602.sql,line=3,col=24,endLine=3,endColumn=28,title=Core G-9602%3A Always use the alias name instead of the table name.::Use d instead of dept in leading hint.
::error file=examples/Core-G-9602.sql,line=4,col=8,endLine=4,endColumn=9,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-9603.sql,line=3,col=20,endLine=3,endColumn=24,title=Core G-9603%3A Never reference an unknown table/alias.::Unknown table/alias emps in leading hint.
::warning file=examples/Core-G-9603.sql,line=3,col=25,endLine=3,endColumn=30,title=Core G-9603%3A Never reference an unknown table/alias.::Unknown table/alias depts in leading hint.
::error file=examples/Core-G-9603.sql,line=4,col=8,endLine=4,endColumn=9,title=Core G-3145%3A Avoid using SELECT * directly from a table or view.::Using SELECT * without subquery.
::warning file=examples/Core-G-9604.sql,line=3,col=28,endLine=3,endColumn=34,title=Core G-9604%3A Never use an invalid stats method.::Using invalid stats method faster in table_stats hint.
::warning file=examples/Core-G-9605.sql,line=3,col=36,endLine=3,endColumn=39,title=Core G-9605%3A Never use an invalid stats keyword.::Using invalid stats keyword rec in table_stats hint.
::warning file=examples/Core-G-9605.sql,line=3,col=43,endLine=3,endColumn=46,title=Core G-9605%3A Never use an invalid stats keyword.::Using invalid stats keyword blk in table_stats hint.
::warning file=examples/Core-G-9605.sql,line=3,col=49,endLine=3,endColumn=55,title=Core G-9605%3A Never use an invalid stats keyword.::Using invalid stats keyword rowlen in table_stats hint.