<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
The generic SQL command to do this is:<br>
<br>
<!--?xml version="1.0" encoding="UTF-8"?-->
<pre><code><span class="sql1-reservedword">ALTER</span><span class="sql1-space"> </span><span class="sql1-reservedword">TABLE</span><span class="sql1-space"> </span><span class="sql1-delimitedidentifier">`tableName` </span><span class="sql1-space"></span><span class="sql1-reservedword">CHANGE</span><span class="sql1-space"> </span><span class="sql1-reservedword">COLUMN</span><span class="sql1-space"> </span><span class="sql1-delimitedidentifier">`columnName`</span><span class="sql1-datatype"> </span></code><code><span class="sql1-datatype"><code><span class="sql1-space"></span><span class="sql1-delimitedidentifier">`columnName`</span></code> VARCHAR</span><span class="sql1-symbol">(</span><span class="sql1-number">size</span><span class="sql1-symbol">)</span><span class="sql1-symbol">;
</span></code></pre>
<title>Untitled</title>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="generator" content="SynEdit HTML exporter">
<style type="text/css">
<!--
body { color: #000000; background-color: #FFFFFF; }
.sql1-comment { color: #808080; font-style: italic; }
.sql1-conditionalcomment { color: #808080; font-style: italic; }
.sql1-datatype { color: #800000; font-weight: bold; }
.sql1-defaultpackages { font-weight: bold; }
.sql1-delimitedidentifier { color: #808000; }
.sql1-exception { font-style: italic; }
.sql1-function { color: #000080; font-weight: bold; }
.sql1-identifier { color: #808000; }
.sql1-number { color: #800080; }
.sql1-plsql-reservedword { font-weight: bold; }
.sql1-reservedword { color: #0000FF; font-weight: bold; }
.sql1-space { }
.sql1-sqlplus-command { font-weight: bold; }
.sql1-string { color: #008000; }
.sql1-symbol { color: #0000FF; }
.sql1-tablename { color: #FF00FF; }
.sql1-variable { color: #800080; }
-->
</style>It won't affect existing data if you are growing the field size.
If you shrink it will truncate.<br>
<br>
Kind regards<br>
<br>
Tom<br>
<br>
<div class="moz-cite-prefix">On 31/07/2014 14:13, Ai Austin wrote:<br>
</div>
<blockquote cite="mid:53da413a.0330c20a.30eb.48ea@mx.google.com"
type="cite">At 10:03 31/07/2014, Tom Mettam wrote:
<br>
<blockquote type="cite">I believe it should be VARCHAR(127), since
object descriptions can be 127 characters long.
<br>
</blockquote>
<br>
<br>
Ah thanks Tom ... prims can actually be varchar(255) according to
my schema and I now wonder if the assets "name" field should also
be varchar(64), as it is for Openvue grid just now, or something
else?
<br>
<br>
I see that prims and primitems have varchar(255) for both the name
and description which seems odd as I would think all these should
be the same?
<br>
<br>
I created a fresh data base for Openvue for a new server setup as
recently as May 2013 and loaded content back in then via OARS and
IARs rather than a SQL backup. So I wonder how I got the
varchar(64) description and if anyone else has the same value?
<br>
<br>
Does anyone have the SQL skill to know the command which will
amend the description field to change its size and advise if that
could mess up any existing assets that have a varchar(64) current
description?
<br>
<br>
-- Yuck. I see that in prims the CreatorID can be varchar(255)
presuMably to accommodate HG creators, but that LastOwnerIDis
char(36) yet that also of course can be a HG user. Maybe this
shouLd be a mantis issue as there seems to be a check needed at
least?
<br>
<br>
<br>
<br>
<br>
_______________________________________________
<br>
Opensim-dev mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:Opensim-dev@opensimulator.org">Opensim-dev@opensimulator.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev">http://opensimulator.org/cgi-bin/mailman/listinfo/opensim-dev</a>
<br>
</blockquote>
<br>
</body>
</html>