-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tim Starling schrieb:
In 1.5 (assuming there are no objections), image
width, height and bit
depth will be available in the image table of the database. This is
mainly for scalability. It allows replication and read load distribution
of this commonly requested data to be handled by the database, where we
already have tools for such things. A simple future extension would be
to bundle metadata queries for all images to be displayed on a page into
a single query. This is only a few lines away now, but was not possible
with the original NFS-based system.
Nice! While you're at it, would it make sense to include a field for the
media type (not the file type) as well? Like, "image", "audio",
"video",
coded as integer values.
That would make (interface to-be-written) searches for media easier on
the database, compared to
... WHERE img_name LIKE "%.jpg" OR img_name LIKE "%.jpeg" OR
img_name
LIKE "%.png" OR img_name LIKE "%.gif" OR img_name LIKE
"%.tif"
Magnus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (MingW32)
Comment: Using GnuPG with Thunderbird -
http://enigmail.mozdev.org
iD8DBQFCWiXSCZKBJbEFcz0RArhGAJ4qWapQIPHiIvtP0dUhVnPMUQTEsgCfToCh
YZCou0YR0RJBA9/TFyNBSC4=
=H3E6
-----END PGP SIGNATURE-----