Home/ Questions/Q 4578122
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T20:26:28+00:00

I was wondering if it would be a good idea to store the dimensions

  • 0

I was wondering if it would be a good idea to store the dimensions of the image in the db in the table where i will be storing the path.

OR –

Should it be better just to check this at run-time and then put those values in a variable and calculate everything at run-time.

OR –

Would it be better to do this through MSSQL.

Also to better explain.

I have an equation which is using image height, image width, row,column to position the seats also there will be the factor of spacing in this equation so that it will come out perfectly.

Hope that this is understandable.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Enzero,

    Hmmm, it’s really impossible to answer that question ACURRATELY without more information; but in general, it’s a good idea to keep your metadata with your data… and metadata which can be worked-out “on the fly” generally should be, to avert any future headaches with the metadata getting out of sync.

    An image size is a strange thing to want to store… it’s in the image-file itself, surely. What format is the image? Or am I missing something?

    Cheers. Keith.

    EDIT:

    After a bit of discussion back-and-forth, Enzero says he’ll try this approach:

    Store the image itself as a BLOB (not just the path to a file containing the image) and it’s height & width (etc) in the seat_status table. When the application starts-up it will load the seat_status’s into a cache, for fast reference thereafter.

    Cheers. Keith.

    PS: You’re welcome Enzero… happy to be of service.

    • 0