Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The answer to your question's title is "yes": I recommend never using <code>from ... import *</code>, and I discussed the reasons in another very recent answer. Briefly, qualified names are <em>good</em>, barenames are very limited, so the "third option" is optimal (as you'll be using qualified names, not barenames) among those you present.</p> <p>(Advantages of qualified names wrt barenames include ease of faking/mocking for testing purposes, reduced to nullified risk of unnoticed errors induced by accidental rebinding, ability to "semi-fake" the top name in a "tracing class" for the purpose of logging exactly what you're using and easing such activities as profiling, and so forth -- disadvantages, just about none... see also the last-but-not-least koan in the Zen of Python, <code>import this</code> at the interactive interpreter prompt).</p> <p>Equally good, if you grudge the 7 extra characters to say <code>QtCore.whatever</code>, is to abbreviate -- <code>from PyQt4 import QtCore as Cr</code> and <code>from PyQt4 import QtGi as Gu</code> (then use <code>Cr.blah</code> and <code>Gu.zorp</code>) or the like. Like all abbreviations, it's a style tradeoff between conciseness and clarity (would you rather name a variable <code>count_of_all_widgets_in_the_inventory</code>, <code>num_widgets</code>, or <code>x</code>? often the middle choice would be best, but not always;-).</p> <p>BTW, I would not use more than one <code>as</code> clause in a single <code>from</code> or <code>import</code> statement (could be confusing), I'd rather have multiple statements (also easier to debug if any import is giving problem, to edit if you change your imports in the future, ...).</p>
    singulars
    1. This table or related slice is empty.
    1. POShould wildcard import be avoided?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USAlex Martelli
    1. USAlex Martelli
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POShould wildcard import be avoided?
      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. COThanks, that's a lot helpful info
      singulars
      1. PO
      1. USColin
    2. COAnother advantage of qualified - you can't import everything in a huge lib like PyQt, and then accidentally cause a namespace collision with something you didn't know was there.
      singulars
      1. PO
      1. USuser106514
    3. COmaybe there is a typo, "import from this" -> "import this"
      singulars
      1. PO
      1. USsunqiang
 

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