Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Others have explained the technical differences. I'll try to explain why you might want to use class variables.</p> <p>If you're only instantiating the class once, then class variables effectively <em>are</em> instance variables. However, if you're making many copies, or want to share state among a few instances, then class variables are very handy. For example:</p> <pre><code>class Foo(object): def __init__(self): self.bar = expensivefunction() myobjs = [Foo() for _ in range(1000000)] </code></pre> <p>will cause expensivefunction() to be called a million times. If it's going to return the same value each time, say fetching a configuration parameter from a database, then you should consider moving it into the class definition so that it's only called once and then shared across all instances.</p> <p>I also use class variables a lot when memoizing results. Example:</p> <pre><code>class Foo(object): bazcache = {} @classmethod def baz(cls, key): try: result = cls.bazcache[key] except KeyError: result = expensivefunction(key) cls.bazcache[key] = result return result </code></pre> <p>In this case, baz is a class method; its result doesn't depend on any instance variables. That means we can keep one copy of the results cache in the class variable, so that 1) you don't store the same results multiple times, and 2) each instance can benefit from results that were cached from other instances.</p> <p>To illustrate, suppose that you have a million instances, each operating on the results of a Google search. You'd probably much prefer that all those objects share those results than to have each one execute the search and wait for the answer.</p> <p>So I'd disagree with Lennart here. Class variables are <em>very</em> convenient in certain cases. When they're the right tool for the job, don't hesitate to use them.</p>
    singulars
    1. This table or related slice is empty.
    1. PODifference between defining a member in __init__ to defining it in the class body in python?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USKirk Strauser
    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. This table or related slice is empty.
 

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