Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Yes, if you're storing int values and then re-retrieving those same int values later then it doesn't matter how they're stored underneath (e.g., big/little endian).</p> <p>For example, suppose you define</p> <pre><code>int a = 0xaabbccdd; </code></pre> <p>On a little endian system this will be stored as <strong>0xdd 0xcc 0xbb 0xaa</strong> in memory. On a big endian system this will be stored as <strong>0xaa 0xbb 0xcc 0xdd</strong>. However, when you view this memory as an <strong>int</strong> it will always be viewed as 0xaabbccdd. Now, if you viewed sub-portions of the original memory (e.g., a sub portion of the int value in memory) endianness would come into play. For example, suppose you only read the first two bytes from the memory location where the int is stored:</p> <pre><code>int *ptr = &amp;a; short firstTwoBytesInMemory = *(short*)ptr; </code></pre> <p>The value of firstTwoBytesInMemory will be 0xccdd on a little endian system, and 0xaabb on a big endian system.</p> <p><strong>Update:</strong> To extend this further, structs are essentially collections of primitive types (e.g., bytes, ints, pointers to other things, etc.). These primitive types are usually laid out in memory contiguously (with some exceptions for alignment, etc). So the same rules that apply to the int/short example above apply to collections of primitive types (e.g., structs).</p> <p>If you start accessing sub-portions of variables then the endianness of the architecture will matter, but if you always deal with things in their correct types (e.g., int, double, etc.) in their entirety the way things are stored underneath should be transparent.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs the address of an int the same in little and big endian?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmattnedrich
    1. USmattnedrich
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. CO@Klas He's casting bytes in memory to ints (on the same int boundaries that the original data was constructed)
      singulars
      1. PO
      1. USmattnedrich
    2. COIt's not "viewed with the MSB first", it's viewed with the MSB most significantly! There isn't a "first" or "last" about the bytes inside the int, it's just an int - it could be stored in absolutely any way the architecture chooses (eg interleaving digits in some crazy way).
      singulars
      1. PO
      1. USNicholas Wilson
    3. COThat's true, what I was trying to say (perhaps in a not very clear way) is that if you store ints and then read them later as ints on the same int boundaries that you created them on you'll always get the same values. However, if you start reading portions of the original data what you will get will depend on how the architecture stores its memory.
      singulars
      1. PO
      1. USmattnedrich
 

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