Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I was typing an answer as David Heffernan just beat me to it. Still while at it i would like to add;</p> <p>Realize that in your first code example you are using a record (TSprite) to hold an object (TImage). TImage is a visual component actually, but ultimately it descends from TObject.</p> <p>A <strong>record</strong> is like most variables (such as Integer) in that it does not have to be instantiated and can be copied at will.</p> <p>An <strong>object</strong> however is a pointer to an instance, and must be created/destroyed by following these steps</p> <pre><code>rec.Image := TImage.Create(nil); // do other things.. rec.Image.Free; </code></pre> <p>And thus may result in memory leaks or Access Violation errors if not done properly. (for example while copying a TSprite..) There is a lot of things that can go wrong in this setup, so therefore i say;</p> <h3>Using objects in records can get tricky. Consider keeping objects in objects:</h3> <p>A simple solution (if you indeed want to keep an instance or pointer reference of TImage inside a TSprite) would be to make TSprite also an object. It could keep track of of creating/destroying automatically by using its constructor and destructor:</p> <pre><code>TSpriteObject = class(TObject) public Image : TImage; constructor Create; destructor Destroy; override; end; </code></pre> <p>and its implemenation:</p> <pre><code>constructor TSpriteObject.Create; begin Image := TImage.Create(nil); // ^ TImage is a component and expects an Owner component that would also // destroy it, so we use a nil value to disable that behavior. end; destructor TSpriteObject.Destroy; begin Image.Free; end; </code></pre> <p>You can then have a TObjectList keep track of many instances of TSprite, and it'll destroy any TSprite (which destroys its TImage) when the list is cleared or destroyed.</p> <p>(this is my first ever stackoverflow post attempt, please bear with me while i find out what i'm doing wrong here)</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to create a record at runtime in delphi
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USBarry Staes
    1. USBarry Staes
    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. COWelcome to stackoverflow. And thanks for answer.
      singulars
      1. PO
      1. USKobus Vdwalt
    2. COThis answer is exceedingly similar to mine. I expect that's just a coincidence because, after all, the points we both make are obvious. I note that your destructor needs to be marked with `override`. You should consider calling inherited in your constructor/destructor. That's always good practice. And you mean *bear* rather than *bare*. If it's alright by you, I won't be baring anything here on SO! ;-)
      singulars
      1. PO
      1. USDavid Heffernan
    3. COThanks Kosus, David, updated my answer. Its no coincidence i agree with your answer, while typing my answer i removed a few paragraphs because you covered that better. Intention of my answer was to point out the memory-leak and AV dangers of records referencing objects.
      singulars
      1. PO
      1. USBarry Staes
 

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