--- Andy Bakun <[EMAIL PROTECTED]> wrote:
> On Sat, 2005-02-19 at 23:55, David Blomstrom wrote:
>
> > > Why not set columns to NOT NULL and default to
> space
> > > for character and 0
> > > for numeric?
> >
> > OK, you're suggesting I...
> >
> > 1. Set all the columns to NOT NULL
> > 2. Set
On Sat, 2005-02-19 at 23:55, David Blomstrom wrote:
> > Why not set columns to NOT NULL and default to space
> > for character and 0
> > for numeric?
>
> OK, you're suggesting I...
>
> 1. Set all the columns to NOT NULL
> 2. Set 0 as the default for numeric fields
> 3. Set "space" for the defau
--- Alex S Moore <[EMAIL PROTECTED]> wrote:
> David Blomstrom wrote:
>
> > So I THINK I may have a good idea for a
> workaround. I
> > simply change all my fields to NOT NULL, then fill
> > every cell that would ordinarily be NULL with a
> unique
> > constant, like 606060.
> >
> > Then I find s
I'm having a terrible time with MySQL's new collation
feature. It frequently fills cells that should be NULL
with 0's and pushes data from one column to another. I
can usually import csv files into my tables using
either Navicat or phpMyAdmin, but I have to experiment
with a lot of settings, and so
