Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We usually have some concrete directory for saving images (like /public_html/images) and there we store the originals (usually resized to some max. size - say 1024px - upon uploading). There are also subdirectories there, called medium and small (for product detail and small thumbnail for category list). </p> <p>We also store the images using products primary key (if products:images is 1:1) or using PK + id (for 1:N). Then we easily assemble the url in img() view helper like this.</p> <pre><code>public function img($product, $imageId, $size = self::SMALL) { return sprintf('/images/%s/%s_%s.jpg', $size, $product-&gt;id, $imageId); } //in view - can also be wrapped in view helper - depends on your scenario &lt;a href="&lt;?php echo $this-&gt;img($product, 1, 'big');?&gt;"&gt;&lt;img src="&lt;?php echo $this-&gt;img($product, 1, 'small');?&gt;" /&gt;&lt;/a&gt; </code></pre> <p><strong>Edit:</strong> BTW: Actually we never use the originals. We make "big" sized images. </p> <p>The action helper for image resizing is generally a good idea. But depends on how you upload your images - if there is only one action and one controller - there is no need AFAIK. But you may want to upload images also from import, using FTP upload, etc. </p> <p>The linking (if the process described abowe doesn't work well for you) of images via DB falls to two categories - content centric and image centric. </p> <p>You can either go into product editing, where is a button or like "upload a new image" or "link uploaded image". Other option is to have a list of images with "connect to a product". Highly dependable on your users' workflow. </p> <p>Also there are some options how to build your db. You can have image_id in your product table. Or you can have imalelink_id in you product table, which links to M:N table that connects images to products. Also you can have product_id in your image table :) All of these approaches are valid in some cases and wrong in some other. All depends on how the end users will use it. </p>
    singulars
    1. This table or related slice is empty.
    1. POZend and phpThumb - Upload Images of a given product or article
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTomáš Fejfar
    1. USTomáš Fejfar
    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
    1. COIt seems a very nice approach as well. You need then, to call that image, later on some specific views, right? So, you echo the returned value from your view helper on each view. Or am I not getting something? Thanks
      singulars
      1. PO
      1. USMEM
    2. COgot it. :) thanks for the clarifications. One last question: :) What are those /%s/%s_%s for ? Thanks again.
      singulars
      1. PO
      1. USMEM
    3. COIt's normal `sprintf()` syntax. I like to use it as it's easier to read: `sprintf('<a href="%s">%s</a>', $url, $title)` then `'<a href="' . $url . '">' . $title . '</a>'` I'm also much less likely to make a mistake in the markup that way.
      singulars
      1. PO
      1. USTomáš Fejfar
 

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