Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p><strong>EDIT</strong>: <em>This is not really answering the question as pointed in the comments. I'll just leave the post here in the case it's useful anyhow...</em></p> <p>I think this is pretty much a matter of syntax unification towards a better usable interface. When providing such member functions without differentiating the name and letting only the overload resolution mechanism determine the correct version you prevent (or at least try to) the programmer from making <code>const</code> related worries.</p> <p>I know this might seem contradictory, in particular given your example. But if you think on most of the use cases it makes sense. Take an STL algorithm like <code>std::equal</code>. No matter whether your container is constant or not, you can always code something like <code>bool e = std::equal(c.begin(), c.end(), c2.begin())</code> without having to think on the right version of begin and end.</p> <p>This is the general approach in the STL. Remember of <code>operator[]</code>... Having in the mind that the containers are to be used with the algorithms, this is plausible. Although it's also noticeable that in some cases you might still need to define an iterator with a matching version (<code>iterator</code> or <code>const_iterator</code>).</p> <p>Well, this is just what comes up to my mind right now. I'm not sure how convincing it is...</p> <p><em>Side note</em>: The correct way to use constant iterators is through the <code>const_iterator</code> typedef.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy does operator ++ return a non-const value?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLeandro T. C. Melo
    1. USLeandro T. C. Melo
    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. VTDownMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUndeletion
    1. COThis is really irrelevant. `std::equal` will take the iterator by value, completely negating any constness that that specific iterator value might have.
      singulars
      1. PO
      1. USPuppy
    2. CO@DeadMG - Maybe you missed the spot...? The point is that if you are in a context in which you have a reference-to-const to a container and you need to call std::equal, for example, you don't have to worry about calling such a c.beginConstVersion() function, you can simply call c.begin() and the compiler will do the trick.
      singulars
      1. PO
      1. USLeandro T. C. Melo
    3. CO@Itcmelo: Except that that is done by returning a `const_iterator`, not a `const iterator`. The question, and the semantics behind it, have nothing to do with accessing the container- they're about accessing the *value* returned by a function. That's true irrespective of if it's a reference or a const/mutable reference.
      singulars
      1. PO
      1. USPuppy
 

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