Open GoogleCodeExporter opened 9 years ago
Hi,
In general, we are considering taking all the the string limits off the spec,
since there are many issues like this.
Original comment by willard....@gtempaccount.com
on 17 May 2011 at 1:44
I'm leery about removing all length restrictions from fields - or unbounded
fields in general. Past bad experiences with garbage data entering systems,
especially given that many of our data types will effectively end up as
basically being not much more than "String" of some sort or another.
In this particular case, 39 characters is I think a nice flag that the field
can contain either IPv4 or IPv6 values, since else I guarantee you we'll see a
bunch of people only setup to expect/parse IPv4, regardless of what the docs
say.
Original comment by j...@shao.org
on 18 May 2011 at 10:28
Original comment by js...@pulsepoint.com
on 18 May 2011 at 10:29
Original comment by js...@pulsepoint.com
on 18 May 2011 at 10:29
Original issue reported on code.google.com by
patrik.o...@admeta.com
on 17 May 2011 at 10:34