Re: Referencing Horde_Shares from other entities

Michael J Rubinsky <[email protected]> Sun, 29 Oct 2017 19:09:17 +0000
Newsgroups gmane.comp.horde.devel
Message-ID <20171029190917.Horde.Qbp3J6AZZEkJ8k4Wnm79XNK@h4.theupstairsroom.com>
Quoting Ralf Lang <[email protected]>:

> Hallo,
>
> for Horde_Shares, it seems like there are two distinct concept - the
> share_name, which usually is not an actual name but a random string and
> the share_id which seems to be a simple autoincrement key.
>
> It looks like in almost all cases, the preferred key to reference a
> share is by share_name rather than share_id.
>
> Is it safe to ignore the share_id and always go for the share_name in
> new code?

IIRC, the id is needed only when considering parent/child hierarchies.



> --
> Ralf Lang
> Linux Consultant / Developer
> Tel.: +49-170-6381563
> Mail: [email protected]
> B1 Systems GmbH
> Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
> GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
> --
> dev mailing list
> Frequently Asked Questions: http://wiki.horde.org/FAQ
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
(unnamed) (application/pgp-keys, 9.1 KB) - not displayed
signature.asc (application/pgp-signature, 821 B)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4

iQIcBAABAgAGBQJZ9iddAAoJEJGSgkbRsxbbN1sP/A099knO+rid9LjAm4i4Nk8F
p01PUfHJMUfEqbWETgI2cI9MhICr0BJu/STfyYS3HxBmZfca3H5bRIrd2i3G3l1S
mt7E8n8Zl470vSEJnHMTjSE0M8jqEpALPTaWICEAKqy52hJJN/4ApUKg5UNfcjVw
g9om+4oLR6Bb8AiUVkFPq1LLJN8JHsY3pQcJxpqme+7i4fS7FMZz+/XJdb6mf0KS
WC5VgcgDV5iZ4jCr+/hJIxucsH9o3WgvZGOVnLyEF/QG1oazGeyJ75MfY8b/zYxE
dXTlZRCfV9Ft8NJ8zgCKWFy5ASjbw+2au9e+lAkqmaKaAGbnPPW5g8C4xmEqbiOC
GEoigrGZ1vOXoVmcCScGXQhP1EmWrpZ5CzgVpJ7D+MOANLvqrqGfqM5P4W/64uJ/
E6r5fztEfrxNw1Jie+NQ2IiOYpb5yVMZOYrFMCdhdHjqqjrjCO+nVuQTqIxN3I1Q
puY8GLnOJfQ4jNMujHAt3+42m0pvfgomfu8s9ER8mrJYM5aKZXgQfUBH7iDgnAAg
xFZMm+E7Agu9p7D/dduraaRTqn+SCqAM3rjmQEACEJKZffbcqJqAXGr/khTKKALl
gbBefFuIdrhG7Isfn0yL233kKJ5NRJtFZL5nLJGmnKDiFvF9WsW9Jw/kmskCMbcZ
x9xj2ODrDNsWGk3Su30q
=EY//
-----END PGP SIGNATURE-----