Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.php > #6047
| Date | 2012-05-14 21:48 +0200 |
|---|---|
| From | Luuk <luuk@invalid.lan> |
| Newsgroups | comp.lang.php |
| Subject | Re: pgsql and exception |
| References | (3 earlier) <a1cdojFsjmU2@mid.uni-berlin.de> <jor217$nnm$3@dont-email.me> <4fb11e73$0$21933$426a74cc@news.free.fr> <jor7q2$tbv$1@dont-email.me> <4fb152f8$0$702$426a74cc@news.free.fr> |
| Message-ID | <654889-bnu.ln1@luuk.invalid.lan> (permalink) |
On 14-05-2012 20:46, Une Bévue wrote: > On 14/05/12 17:19, Shake wrote: >> Links, You mean URL? have no limit. It don't need to be longs, but it >> can. There is any requirement of use a "small" varchar(256) for this >> field? >> >> IF there is no limitation or requirement, perhaps is better to put >> enough space to avoid problems. varchar(1024) could no make a big >> diference if you don't have a really enormous amount of data. > > Yes I mean url for link, a simple google maps URL gave me strlen($url) = > 329 > > I have to be more generous... not too generous ;) http://dev.mysql.com/doc/refman/5.5/en/char.html "In contrast to CHAR, VARCHAR values are stored as a one-byte or two-byte length prefix plus data. The length prefix indicates the number of bytes in the value. A column uses one length byte if values require no more than 255 bytes, two length bytes if values may require more than 255 bytes. " Changing the length from 256 to 1024, or even 2048, should only make a difference if you store a lot of those lengthy urls...
Back to comp.lang.php | Previous | Next — Previous in thread | Find similar | Unroll thread
pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 08:39 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 09:10 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-14 09:34 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 14:17 +0200
Re: pgsql and exception Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-14 09:38 -0400
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 16:59 +0200
Re: pgsql and exception "Álvaro G. Vicario" <alvaro.NOSPAMTHANX@demogracia.com.invalid> - 2012-05-14 09:45 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-14 10:18 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 14:24 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-14 14:54 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 15:03 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-14 14:56 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 15:26 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-14 22:33 +0200
Re: pgsql and exception "M. Strobel" <sorry_no_mail_here@nowhere.dee> - 2012-05-15 09:32 +0200
Re: pgsql and exception Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-14 09:40 -0400
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 17:02 +0200
Re: pgsql and exception Shake <QUITAESTO@QUITAESTO.NOES> - 2012-05-14 17:19 +0200
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-14 20:46 +0200
Re: pgsql and exception Jerry Stuckle <jstucklex@attglobal.net> - 2012-05-14 14:55 -0400
Re: pgsql and exception Une Bévue <unbewusstsein@fai.invalid> - 2012-05-15 08:00 +0200
Re: pgsql and exception Luuk <luuk@invalid.lan> - 2012-05-14 21:48 +0200
csiph-web