Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I would have thought that the compiler would complain about parse taking a <code>char*</code> as its second argument, since you actually provide a <code>const char*</code> (i.e. a string constant). However, you actually try to copy the string, so you could have (and should have) made the prototype <code>const char*</code>.</p> <p>Let's focus on "try to copy". Leaving aside your obfuscated initialization, what you do is:</p> <pre><code> inputstr = malloc (sizeof(str)); strcpy(inputstr, str); </code></pre> <p>Before I go any further, I suggest you look at <code>strdup</code>, which does exactly what you want, only correctly:</p> <pre><code> inputstr = strdup(str); </code></pre> <p>No fuss, no errors. But anyway,</p> <p><code>str</code> is a <code>char*</code>; that is, a pointer to a character. (It should have been <code>const char*</code>, but it would still be a pointer to a character.) So <code>sizeof(str)</code> is the size of a pointer, which is likely to be four bytes on your platform, although it might be eight. Either way, it's not close to long enough to hold the string <code>"add,9898,Wings,Tasty Wings,14.99\n"</code>, so when you copy that into <code>inputstr</code>, you'll end up overwriting random memory. (And probably again with the <code>del</code> string).</p> <p><code>sizeof(*str)</code> would be the size of a character, which is one byte. What I think you might have meant was <code>strlen(str)</code>, which is the length of the string <code>str</code> in bytes, but that wouldn't be right either because it leaves out the terminating NUL byte.</p> <p>In short, what you wanted was the <code>strdup</code> call above, which is equivalent to:</p> <pre><code>char* inputstr = malloc(strlen(str) + 1); strcpy(inputstr, str); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POStrange character replacement where it makes no sense (to me)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USrici
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POStrange character replacement where it makes no sense (to me)
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COAbsolutely fantastic explanation! As I've said before, the helpful people here at stackoverflow have helped me learn more about programming than most! It turned out to be a rookie error after all; I've been trying really hard to avoid those. But I think I'm improving. Thanks for the detailed explanation!
      singulars
      1. PO
      1. USThanasi Poulos
    2. CO@capncoolio: No worries. By the way, `parse` leaks the memory it allocates for `inputstr`. With your design, you cannot free that memory because you put pointers to pieces of inputstr into your database. So you'll really have to rethink your memory management strategy once you move beyond the "toy" stage. Good luck.
      singulars
      1. PO
      1. USrici
    3. COisn't `inputstr` local to `parse` anyway? Or is this a case of me THINKING I am copying pieces of `inputstr`, when in actual fact I am pointing to places in each instance of `inputstr`?
      singulars
      1. PO
      1. USThanasi Poulos
 

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