Important Announcement

This forum will be discontinued.

The creation of new topics is disabled.

Please open GitHub issues for the corresponding topics/products in the following Trivadis repositories:

A lot of users have already a GitHub account and the management of the issues is better than in this forum. For example, closing a forum topic is never related to a product change. Closing a GitHub issue for an accepted bug means that the bug is fixed. This should simplify the work for all involved parties.

See this blog post for more information.

Thank you for your understanding.

Notifications
Clear all

[Solved] Enforcing naming convention and code commenting practices

 
PL/SQL Cop
Last Post by diordonez 8 years ago
4 Posts
2 Users
1 Reactions
2,445 Views
RSS
0
12/06/2017 9:30 pm
Topic starter
diordonez 
(@diordonez)
Active Member
7 Posts
4 0 3

Hi.

 

Is there any option in PL/SQL Cop to enforce the naming conventions ? for instance that a cursor must be named "c_employees", and so on ?

The same question for code commenting and coding style. Does the tool enforce these guidelines ?

 

Thank you

1 Answer
0
12/06/2017 10:05 pm
Philipp Salvisberg 
(@phs)
Admin
  Trusted Member
50 Posts
0 40 9

Is there any option in PL/SQL Cop to enforce the naming conventions ? for instance that a cursor must be named "c_employees", and so on ?

Not directly. However, since version 2 PL/SQL Cop support custom guidelines. A sample validator is provided as Maven project covering the chapter "2.2 Naming Conventions" of  Trivadis PL/SQL & SQL Coding Guidelines Version 3.2. Have a look at the OTN discussion about this topic. Just configure the validator "com.trivadis.tvdcc.validators.TrivadisGuidelines3Plus" instead of "com.trivadis.tvdcc.validators.GLP" as described in this post. 

The same question for code commenting and coding style. Does the tool enforce these guidelines ?

Currently there are no validators available covering chapter "3. Coding Style".

diordonez Topic starter 12/06/2017 10:26 pm

Awesome Philipp, thanks for your quick reply.

 

Is the "jar" plugin already available anywhere ? or do I have to actually produce it with Maven.

 

All the best

 
Philipp Salvisberg 13/06/2017 5:36 am

No, you have to build the validators.jar with the Maven build file.

 
diordonez Topic starter 14/06/2017 12:37 am

Thanks a lot. With the instructions you provided in this link:

 

https://community.oracle.com/message/14386256#14386256

 

Everything worked as expected.

Cheers

 
Forum Jump:
  Previous Topic
Next Topic