Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <ul> <li>It's up to you, just doing <code>buffer</code> is more terse but if it were a <code>vector</code>, you'd need to do <code>&amp;buffer[0]</code> anyway.</li> <li>Depends on your intended platform.</li> <li>Does it matter? Have you determined it to be a problem? Write the code that's easiest to read and maintain before you go off worrying if you can obfuscate it into something faster. But for what it's worth, allocation on the stack is very fast (you just change the stack pointer value.)</li> <li>You should be using <code>std::string</code>. If performance becomes a problem, you'd be able to reduce dynamic allocations by just returning the internal buffer. But the <code>std::string</code> return interface is way nicer and safer, and performance is your last concern.</li> <li>That's a memory leak. Many will argue that's okay, since the OS free's it anyway, but I feel it terrible practice to just leak things. Use a static <code>std::vector</code>, you should <em>never</em> be doing any raw allocation! If you're putting yourself into a position where you might leak (because it needs to be done explicitly), you're doing it wrong.</li> <li>I think your (1) and (2) just about cover it. Dynamic allocation is almost always slower than stack allocation, but you should be more concerned about which makes sense in your situation.</li> <li>You shouldn't be using those at all. Use <code>std::string</code>, <code>std::stringstream</code>, <code>std::copy</code>, etc.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. PODealing with char buffers
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGManNickG
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI always forget that I can use a std::vector a creating a buffer with malloc/new. Thanks for reminding me :) I agree that C++ constructs should be preferred but I like to make an exception for sprintf/printf. I find it more elegant than littering my code with stream operators.
      singulars
      1. PO
      1. USStackedCrooked
    2. CO@Stack: You should use Boost.Format then, or wrap things into a function like `boost::lexical_cast`.
      singulars
      1. PO
      1. USGManNickG
 

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