Skip to Main Content

Java EE (Java Enterprise Edition) General Discussion

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Etiquette

brjavamanOct 12 2015

This Etiquette guide is co-opted from Rich Hickey's post to the Clojure mailing list some time ago.

The Adopt a JSR programme (and its mailing lists and IRC channel) are run by, and for, people who make things or contribute their time in other positive ways to the Adopt a JSR programme.

Most messages should have one of these themes:

  • I'm adopting a JSR - here is my contribution
  • I am trying to adopt a JSR and am having trouble, please help
  • I can help you with that JSR
  • I am trying to make something work for a JSR and am having trouble, please help
  • I can help you adopt a JSR

They are not the place for opinion pieces and diatribes.They are not the place for massive legal and political debates. If there is a particular legal/political concern about a particular JSR then some limited discussion is fine, but it should not dominate the list/channel.Occasionally, there may be disagreements about how a JSR has been, or will be, made. These disagreements should take the form of technical arguments. To make a technical argument that gets (and gives!) respect:

  • Keep it short
  • Stick to the facts
  • Use logic
  • Leave people out of it
  • Avoid rhetorical devices:
    • Superfluous or opinion-laden adjectives
    • Claims to speak for the community, or that everyone agrees with you.
    • Threats of what will happen unless things go your way
    • Any flavor of 'the sky is falling'

If you are not working on that JSR, you should restrict your input to very short technical arguments supporting your position. If someone has already made your point, just +1 it.

Please keep your posts short.

Ignoring these guidelines fails to respect the time and effort of people who are trying to make a positive difference, which you should care about if you intend to be one.

Comments

WITH dup_count AS( SELECT
    t.*,
    COUNT(*) over (PARTITION BY col1, col2, <add_your_columns_here>) c
FROM tab1 t )
SELECT * FROM dup_count
 WHERE c > 1;

Use Analytics function.

1 - 1

Post Details

Added on Oct 12 2015
0 comments
1,582 views