From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-webteam/2011-October/001379.html | 111 ++++++++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 zarb-ml/mageia-webteam/2011-October/001379.html (limited to 'zarb-ml/mageia-webteam/2011-October/001379.html') diff --git a/zarb-ml/mageia-webteam/2011-October/001379.html b/zarb-ml/mageia-webteam/2011-October/001379.html new file mode 100644 index 000000000..1e7b6e358 --- /dev/null +++ b/zarb-ml/mageia-webteam/2011-October/001379.html @@ -0,0 +1,111 @@ + + + + [Mageia-webteam] [Bug 998] O Brother, Where Art Thou? + + + + + + + + + +

[Mageia-webteam] [Bug 998] O Brother, Where Art Thou?

+ Buchan Milne + bugzilla-daemon at mageia.org +
+ Wed Oct 5 13:46:49 CEST 2011 +

+
+ +
https://bugs.mageia.org/show_bug.cgi?id=998
+
+Buchan Milne <bgmilne at zarb.org> changed:
+
+           What    |Removed                     |Added
+----------------------------------------------------------------------------
+                 CC|                            |bgmilne at zarb.org
+
+--- Comment #10 from Buchan Milne <bgmilne at zarb.org> 2011-10-05 15:46:48 CEST ---
+> Country/city can already be done with localityName and countryName, but no
+> schema seems to use it so far.
+
+'l' is an alias for 'localityName', and organisationalPerson->inetOrgPerson has
+it. They also have 'st' for 'state' and 'postalCode'
+
+It would be relatively easy to add support for additional attributes to hold
+locality data (e.g. adding contryName or 'c' is relatively trivial).
+
+To do it properly, we should request an enterprise number from IANA so we can
+have viable schema definitions (that can be published).
+
+The biggest issue is how to store coordinates, e.g. as as plain string, or as
+attributes dedicated for longitude or latitude (which impacts whether you can
+easily store multiple values).
+
+> Otherwise, yes, having a dedicated small db for this would make it. Do we need
+> more than these two relationships?
+>  * user lives in place (or even places but that makes it out of LDAP I think,
+let's keep it simple)
+
+Easy if we don't consider coordinates, we use a multi-valued attribute.
+
+'l' or 'localityName' is multi-valued.
+
+[bgmilne at tiger bgmilne]$ ldapsearch -LLL uid=bgmilne l 2>/dev/null
+dn: uid=bgmilne,ou=People,dc=ranger,dc=dnsalias,dc=com
+l: Cullinan
+l: Centurion
+l: Lagos
+l: Cape Town
+
+> * place has coordinates
+
+If you want to store one, no problem. Many options open, format being the
+biggest issue to worry about (decimal or not).
+
+If you want multiple ones, easy if latitude and longitude stored together as a
+single string, or using any other coding that results in unique strings.
+
+If you want to associate to localityName's, more difficult.
+
+-- 
+Configure bugmail: https://bugs.mageia.org/userprefs.cgi?tab=email
+------- You are receiving this mail because: -------
+You are the QA contact for the bug.
+
+ + + +
+

+ +
+More information about the Mageia-webteam +mailing list
+ -- cgit v1.2.1