Re: [Envolution-devel] SPChat, NS-User, RTE_Multi

[<s.k...@pr...>]

@Arden:
Please remember that we support Oracle.
For the Oracle installation the fields pn_user_sig and pn_bio are defined as
VARCHAR2(255).
Oracle doesn't know anything of "tinytext" or "longtext".
The problem is, that the maximum length under Oracle is 255.
Other solution is, to change the field definition to "text" so we can define
it for Oracle as CLOB.

But your mods in Users looks very nice. Your idea to use user_sig and bio
for detailed personal infos like an application writing down and personal
record is new. Nobody ask for such a feature.
Nevertheless, it would be a good thing and gives a new meaning to the
fields.

WindMeUp
[eNvo-Dev team]
[Lead Developer]


----- Original Message -----
From: "Arden Wiebe" <ar...@li...>
To: "eNvolution" <env...@li...>
Sent: Friday, July 18, 2003 2:58 AM
Subject: Re: [Envolution-devel] SPChat, NS-User, RTE_Multi


> > I changed the table structure in the envo_user table for pn_user_sig and
> > pn_bio both to longtext from their original to handle the extra bulk.
> > Does anyone see anything wrong with the data types for those two fields
> > that I have altered?
>
> When someone has a minute can I get some feedback on my choice of data
> type for these fields.  I'm wondering why original development had the
> fields pegged at 255 varchar for the user_sig and tinytext for the bio.
>
> Also if you expand all the fields in the Members_List module fileds like
> bio and user_sig are not set for display.  I ran into this trying to
> implement more search functionality for my members.
>
> To see what the SPChat, RTE_Multi does for a user profile check this
> link out:
>
> http://www.workwanted.ca/user.php?op=userinfo&uname=Admin
>