Thread: [phpesp-dev] group (realm) name

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I'm needing longer group (realm) names.  If I change the realm.name 
from char(16) to varchar(255) do you know of anything that will be 
broken?

chad.

should work! but it´s more risky in other reasons! secure things
take ids/numbers than long names, i think

kind regards

----- Original Message ----- 
From: "Chad Bearden" <ch...@be...>
To: <php...@li...>
Sent: Thursday, July 03, 2003 4:39 PM
Subject: [phpesp-dev] group (realm) name

> I'm needing longer group (realm) names.  If I change the realm.name
> from char(16) to varchar(255) do you know of anything that will be
> broken?
>
> chad.
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
> _______________________________________________
> phpESP-devel mailing list
> php...@li...
> https://lists.sourceforge.net/lists/listinfo/phpesp-devel
>

Virtually all character limits in phpESP are arbitrary.  Performance 
wise, you will probably do better with char() types than varchar() if 
the column is used for WHERE criteria.  Some limits (field name length = 
10) are cruft from the DBF export option, which doesn't exist in the 
main branch anymore (or ever?).  I do not forsee any problems with 
adjusting any field lengths to suit your need (except possible performance).

-James

Chad Bearden wrote:
> I'm needing longer group (realm) names.  If I change the realm.name from 
> char(16) to varchar(255) do you know of anything that will be broken?
> 
> chad.

Another thing (that James may be alluding to in the previous post):

Char is nearly always better than varchar for speed in mysql (where char is
possible of course), however varchar may result in smaller tables (disk
size). 

This is because Varchar results in the table having dynamic record sizes,
which means indexing  is slower (i.e. lookups), where as char allows for
fixed width records (faster).

See:

http://www.mysql.com/doc/en/CHAR.html

Just thought I would throw this in because I know that it is something that
I overlooked for a long long time.