[Rt-devel] schema thought

[Nicholas Clark]

On Tue, Jul 10, 2007 at 09:52:28AM -0700, Jesse Vincent wrote:
> 
> On Jul 10, 2007, at 9:48 AM, Nicholas Clark wrote:

> >Aha - so this is legacy from an installation that was upgraded from  
> >3.4?
> >
> 
> pinglin:~/svk/rt-3.4/etc jesse$ grep Instance schema.* |grep -v INDEX  
> |grep -v ':--'
> schema.Informix:        Instance        INTEGER DEFAULT 0 NOT NULL,
> schema.Oracle:  Instance        NUMBER(11,0) DEFAULT 0 -- NOT NULL
> schema.Pg:  Instance integer,
> schema.SQLite:  Instance integer
> schema.Sybase:  Instance integer,
> schema.mysql:  Instance integer,
> pinglin:~/svk/rt-3.4/etc jesse$ cd ../rt-3.2
> -bash: cd: ../rt-3.2: No such file or directory
> pinglin:~/svk/rt-3.4/etc jesse$ cd ../../rt-3.2/etc/
> pinglin:~/svk/rt-3.2/etc jesse$ grep Instance schema.* |grep -v INDEX  
> |grep -v ':--'
> schema.Informix:        Instance        INTEGER DEFAULT 0 NOT NULL,
> schema.Oracle:  Instance        NUMBER(11,0) DEFAULT 0 -- NOT NULL
> schema.Pg:  Instance integer,
> schema.SQLite:  Instance integer
> schema.Sybase:  Instance integer,
> schema.mysql:  Instance integer,
> 
> I don't have a 3.0 checkout.

Odd. Most strange. How did it come to be a varchar(64);

> But yes, it's safe to fix

Is it safe to make it not null?

Or do some versions of mysql get upset for no logical reason in this case?

Nicholas Clark