Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are right. <code>Constant pool</code> doesn't require <em>duplicate entries</em>. One class should only have 1 entry in the constant pool.</p> <p>This definitely seems to be a bug. Check this out. Someone has logged this as bug and it has been acknowledged >> <a href="http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6746955" rel="nofollow">http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6746955</a></p> <p><strong>Answer Updated:</strong></p> <p>One more thing I want to point out here is that adding duplicate entries does not make any sense because it increases the byte size of the class file and that destroys the main purpose of java class file's compactness, portability and faster network mobility. The class file should be as much compact as possible.</p> <p><strong>By the way</strong>, class file is valid because it adheres to class file format defined. But its not an ideal one.</p> <p>As I forgot to, <strong>answer your second Question:</strong></p> <p>JVM assigns <em>similar looking</em> objects the same hashcode but still they will be distinct. JVM will never create 2 objects identical unless both are referring to same object. Hashcode is nothing but a partition system. Similar looking objects are placed into same partition so that the traversing time becomes less while searching for a particular object. Hashcode is nothing but a pointer to that small partition. </p> <p>Only because it is not possible to assign distinct hashcode to each new object(because number of objects can outnumber possible number of unique hashcode creation. Please refer to possible collision in hash algorithm), you may find distinct objects having same hashcode. But here is the thing, 2 objects pointing to same reference in the memory must have the same hashcode.</p> <p><strong>So</strong>, moral of the story, JVM makes sure that two distinct objects can never be identical even if their hashcodes are.</p>
    singulars
    1. This table or related slice is empty.
    1. POJava class constant pool duplicates?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRavi Trivedi
    1. USRavi Trivedi
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJava class constant pool duplicates?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CODid you look at that bug you linked? It was reported in 2008, and the last activity on it was 2 years ago. Were it actually broken, it'd have been fixed long ago.
      singulars
      1. PO
      1. UScHao
    2. COI wasn't referring to how old it was. I was referring to that bug and the acknowledgment of it. I meant to say, this is indeed a bug.
      singulars
      1. PO
      1. USRavi Trivedi
    3. COIt's an inefficiency....but it's not incorrect.
      singulars
      1. PO
      1. UScHao
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload