Hi, On Thu, 17 May 2007, Tom Lane wrote: <snipp/>
It seems the correct solution here is to extend the inet type to support RFC4007 "zone_id" strings. Yech. Not going to happen as a bug fix, but we should probably put it on the TODO list.
propably yes. But we should bear in mind that addresses of different scopes are not comparable with each other in the sense of apples vs. oranges. i.e: select 'fe80::1%em0'::inet = 'fe80::1%em1'::inet; should return null. Also how do we define sort order if not all values are comparable.
As a temporary workaround, should we hack the server to suppress any %-foo found in the result of getnameinfo()?
Not sure what that would buy us. Stripping the scope from the address does not seem the right thing to do. Extending the generic inet type with scoped addresss is another question. Greetings Christian -- Christian Kratzer CK Software GmbH Email: [EMAIL PROTECTED] Schwarzwaldstr. 31 Phone: +49 7452 889 135 D-71131 Jettingen Fax: +49 7452 889 136 HRB 245288, Amtsgericht Stuttgart Web: http://www.cksoft.de/ Geschaeftsfuehrer: Christian Kratzer ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
