> On Jan 30, 2008 12:50 PM, Dmitry E. Oboukhov wrote:
> > Is it possible to add to the syntax of the INSERT operator appoximately
> > in such way:
> > SELECT list INSERT [IGNORE] INTO ... - an added one.
> > SELECT list UPDATE - an added one.
>
> > PS: I understand that adding the changes i
On Jan 30, 2008 12:50 PM, Dmitry E. Oboukhov wrote:
> Is it possible to add to the syntax of the INSERT operator appoximately
> in such way:
> SELECT list INSERT [IGNORE] INTO ... - an added one.
> SELECT list UPDATE - an added one.
> PS: I understand that adding the changes into a language i
At 12:38 -0700 on 05/27/2004, Daevid Vincent wrote about Re: Feature
Request: UPDATE 'error codes' or mysql_affected:
REPLACE INTO won't work, as I need the previous record (hence the update). I
store the first and last time I saw a node, amongst other info. REPLACE
would d
Daevid Vincent wrote:
Well, my "hack" (which is sort of like what you suggest) is to change my
primary key from just an auto_increment 'id' field to a combination of two
other fields (mac/scanner_id) that I know must be unique. Then I rely upon
the fact that mySQL will not allow a duplicate PK. (I
PLACE
would delete that data.
http://daevid.com
> -Original Message-
> From: Steve Meyers [mailto:[EMAIL PROTECTED]
> Sent: Thursday, May 27, 2004 7:42 AM
> To: Daevid Vincent
> Cc: [EMAIL PROTECTED]
> Subject: Re: Feature Request: UPDATE 'error codes' or
> mysql_a
http://dev.mysql.com/doc/mysql/en/INSERT.html
INSERT [LOW_PRIORITY | DELAYED] [IGNORE]
[INTO] tbl_name [(col_name,...)]
VALUES ({expr | DEFAULT},...),(...),...
[ ON DUPLICATE KEY UPDATE col_name=expr, ... ]
If you specify the ON DUPLICATE
Does REPLACE INTO not work in your case?
|
|
|REPLACE| works exactly like |INSERT|, except that if an old record
in the table has the same value as a new record for a |PRIMARY KEY|
or a |UNIQUE| index, the old record is deleted before the new record
is inserted. See section 14.1.4 |INSE
> Here is the background: Anyone that is running a huge system like MARC
> that has millions of uncompressed blob records in huge tables, needs to be
> able to migrate, in real-time and without down-time, to compressed blobs.
> Therefore, we need a way to know if a given field is compressed or not
Hi!
On Feb 27, Lester Hightower wrote:
> To whom it may concern at Mysql AB:
>
> I see from the Mysql 4.1.1 CHANGELOG that new COMPRESS(), UNCOMPRESS(),
> and UNCOMPRESSED_LENGTH() functions were added. That is great news, and
> something I have been very interested in for a long time, as eviden
Perhaps TIMESTAMP will provide what you need.
Daevid Vincent wrote:
http://www.mysql.com/doc/en/CREATE_TABLE.html states "Default values must be
constants. This means, for example, that you cannot set the default for a
date column to be the value of a function such as NOW() or CURRENT_DATE."
Is t
At 17:56 -0800 3/5/03, Daevid Vincent wrote:
http://www.mysql.com/doc/en/CREATE_TABLE.html states "Default values must be
constants. This means, for example, that you cannot set the default for a
date column to be the value of a function such as NOW() or CURRENT_DATE."
Is this ever going to be "fix
On Sun, 11 Aug 2002 [EMAIL PROTECTED] wrote:
> I have just started using mysql for a database project and I wonder that one
> function is missing. I am using myphpadmin as utility. It is possible to
> write a comment to each table, but it is not possible to write a comment to each
> field. Why not
Hi!
On Dec 12, Colin Faber wrote:
> Hi,
>
> I've got a feature request which I don't think should be all that hard
> to implement (if not already)
>
> With in the mysql fulltext search system if your search words exist in
> more than 50% of the records; it is ignored.
>
> How about having mys
Hi.
MySQL already reserves one connection to users with the process
privilege. So assure that common clients don't have the process
privilege and you connect with one that has it and you are done.
This is documented here (found no other place):
http://www.mysql.com/doc/T/o/Too_many_connections.h
Hi!
> "Basil" == Basil Hussain <[EMAIL PROTECTED]> writes:
Basil> Hi,
>> I am BEGGING you to please make the describe command OPTIONALLY display the
>> Privileges column. Before 3.23, I was able to see the describes properly. Now
>> the command is almost totally useless to me!
Basil> I agr
Hi,
> I am BEGGING you to please make the describe command OPTIONALLY display the
> Privileges column. Before 3.23, I was able to see the describes properly. Now
> the command is almost totally useless to me!
I agree! On any table you care to describe the output is usually always
wider than even
16 matches
Mail list logo
