Hi Shane,
- Original Message -
From: "Shane Allen"
Sent: Wednesday, September 10, 2003 7:16 PM
Subject: FULLTEXT feature requests
> The only reason that we are unable to use a stock build of mysql is
> because
>
> 1) we use GWS_FREQ as our GWS_IN_USE, not GWS_PRO
The only reason that we are unable to use a stock build of mysql is
because
1) we use GWS_FREQ as our GWS_IN_USE, not GWS_PROB
2) we have a custom stopword list
Is there any reason that these two settings, like FT_MIN_WORD_LENGTH,
cannot be moved to runtime-configurable params? Obviously, changin
Mike Wexler writes:
>
>
> Quentin Bennett wrote:
>
>
> >
> > Shell escape
> >
> > mysql> !rm /tmp/data.txt
> > mysql> select col into outfile '/tmp/data.txt' from table;
> >
> >
> >
> > mysql> select col into local outfile '/tmp/data.txt' from table
> >
> >
> >
> > Would these options pr
I'll add my voice especially on the local file. many times I have wanted to
be able to skip creating the file on the server, then having to scp it to my
local box.
On Tuesday 11 December 2001 02:09 pm, you wrote:
> Hi,
>
> I would like to request the addition of the following features to the
>
Quentin Bennett wrote:
>
> Shell escape
>
> mysql> !rm /tmp/data.txt
> mysql> select col into outfile '/tmp/data.txt' from table;
>
>
>
> mysql> select col into local outfile '/tmp/data.txt' from table
>
>
>
> Would these options prove useful to others?
Yes. Especially the local outfil
Hi,
I would like to request the addition of the following features to the
command line client:
Shell escape
mysql> !rm /tmp/data.txt
mysql> select col into outfile '/tmp/data.txt' from table;
The command is run on the client. It would all SQL scripts to be run more
simply that constructing a s
