Roman Vilensky wrote:
Right. I was mistaken about the order in which these happen. I thought it was assign old value, then increment, but it is the other way around.
Tim Moores wrote:Single quotes can be escaped by replacing them with two single quotes:
Tim Moores wrote:Or you can use a PreparedStatement which takes care of this for you.
Bear Bibeault wrote:Correct. Setting a value into the application context will not affect any session.
Liutauras Vilda wrote:
Angus Ferguson wrote:The question popup from a brief discussion I had today where this topic got a mention.
Do you remember what was the context in which it was discussed?
Regarding what Tim said and what I meant afterwards is, it could be that two unequal objects produce the same hashcode (hash collision), hence their keys point to the same bucket, in which case to find particular needed object within such bucket, equals() method is used.
So as per contract, if two objects are equal, they must result in the same hashcode. While two unequal objects may or may not produce different hashcode. Of course in ideal scenario, for unequal objects you want them to have different hashcodes.
Angus Ferguson wrote:
So why use double-slashes?
It has not effect in file paths in fact it is treated as a single path, with Linux for me is more stylish...I find value on it.