Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The only hit should be compile time, but <strong>rday</strong> writes that there is apperently a small hit. But that should be something that Adobe will fix in the future.</p> <p>The import statements should not really be looked on as actual imports, it is merely a way for the compiler to know which classes you are refering to.</p> <p>eg. If you made you own <code>Point</code> class and it was being used in another package, the compiler needs to know if you are refering to your own <code>Point</code> class or the Adobe <code>Point</code> class.</p> <p>The alternative would be to write the fully qualified name evertime you refered to a class.</p> <p>eg. <code>var mySprite:flash.display.Sprite = new flash.display.Sprite();</code></p> <p>As pointed out by <strong>Juan Pablo Califano</strong> in the comment, this does not actually work with the compiler (though I think it might work with AS2). I merely meant to point out why we have import statement to begin with.</p> <p>In any case it should not effect the compiled file if you import a whole package (though it apperently does). It will how ever effect compile time, since you are giving the compiler more stuff it needs to look through.</p> <p>As for "importing" the same class more than once. It will not make a difference. The compiler will only include the same class once. Else the compiled file size would quickly spin out of control, since most classes refer to many classes which again refer to others etc. But again, Adobe might have optimizing to do there.</p> <p>Bottom line is you should only import the stuff you need, there is no real advantage to importing a whole package. Just use a proper coding tool like <a href="http://www.flashdevelop.org/wikidocs/index.php?title=Main_Page" rel="noreferrer">FlashDevelop</a> (it is free) and you do not even have to write the import statements yourself.</p> <p>On a side note, if you are compiling a library (where a class not refered to are also included), im not sure if importing a external package might include that in you compiled file. That might have an actual impact; though hopefully Adobe did not screw up there ;)</p>
    singulars
    1. This table or related slice is empty.
    1. POActionscript 3 import package.* vs import package.Class
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USJacob Poul Richardt
    1. USJacob Poul Richardt
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POActionscript 3 import package.* vs import package.Class
      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. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COJust a note: even if you use the fully qualified path in your code, you need the import or else the compiler will complain.
      singulars
      1. PO
      1. USJuan Pablo Califano
    2. COTrue, I forgot that. But it was more meant as a point as to why we have the import statements, since the alternative would be very annoying.
      singulars
      1. PO
      1. USJacob Poul Richardt
    3. CONo problems. And yes, that was the behaviour in AS 2. If you used the fully qualified name, you could omit the import.
      singulars
      1. PO
      1. USJuan Pablo Califano
 

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