RE: MySQL 4.1.5 has been released

2004-09-22 Thread Prafulla Girgaonkar
Hi Lenz

I could not download it. When I click on DOWNLOAD link, it takes me to some strange 
website.

Prafulla


-Original Message-
From: Lenz Grimmer [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 21, 2004 10:37 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: MySQL 4.1.5 has been released


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

MySQL 4.1.5, a new version of the popular Open Source/Free Software 
Database Management System, has been released. It is now available in 
source and binary form for a number of platforms from our download pages 
at http://dev.mysql.com/downloads/ and mirror sites.

Note that not all mirror sites may be up to date at this point in time -
if you can't find this version on some mirror, please try again later or
choose another download site.

This is the second 4.1 gamma release, mainly fixing recently discovered
bugs in preparation for the upcoming production release.

Please refer to our bug database at http://bugs.mysql.com/ for more
details about the individual bugs fixed in this version.

News from the ChangeLog:

Functionality added or changed:

  * The Windows Installer packages are now making use of the Windows
Installer (MSI) and include a new MySQL Server Instance Configuration
Wizard that can be used to easily generate an optimized server
configuration and to apply core security settings.
  * InnoDB: Added configuration option innodb_autoextend_increment for
setting the size in megabytes by which InnoDB tablespaces are
extended when they become full. The default value is 8,
corresponding to the fixed increment of 8MB in previous versions
of MySQL.

Bugs fixed:
  * Fixed name resolving of external fields of subqueries if subquery
placed in select list of query with grouping. (Bug #5326)
  * Fixed detection of using same table for updating and selecting in
multi-update queries. (Bug #5455)
  * The values of the max_sort_length, sql_mode, and
group_concat_max_len system variables now are stored in the query
cache with other query information to avoid returning an incorrect
result from the query cache. (Bug #5394) (Bug #5515)
  * Fixed syntax analyzer with sql_mode=IGNORE_SPACE. It happened to
take phrases like default .07 as identifier.identifier. (Bug
#5318)
  * Fixed illegal internal field length of user variables of integer
type. This showed up when creating a table as select @variable.
(Bug #4788)
  * Fixed a buffer overflow in prepared statements API
(libmysqlclient) when a statement containing thousands of
placeholders was executed. (Bug #5194)
  * Fixed a bug in the server when after reaching a certain limit of
prepared statements per connection (97), statement ids began to
overlap, so occasionally wrong statements were chosen for
execution. (Bug #5399)
  * Fixed a bug in prepared statements when LIKE used with arguments
in different character sets crashed server on first execute. (Bug
#4368)
  * Fixed a bug in prepared statements when providing '-00-00'
date to a parameter lead to server crash. (Bug #4231, Bug #4562)
  * Fixed a bug in OPTIMIZE TABLE that could cause table corruption on
FULLTEXT indexes. (Bug #5327)
  * InnoDB: Fixed a bug that InnoDB only allowed a maximum of 1000
connections inside InnoDB at the same time. A higher number could
cause an assertion failure in sync0arr.c, line 384. Now we allow
1000, 1, or 5, depending on the buffer pool size. (Bug
#5414)

Bye,
LenZ
- -- 
  Lenz Grimmer <[EMAIL PROTECTED]>
  Senior Production Engineer
  MySQL GmbH, http://www.mysql.de/
  Hamburg, Germany
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFBUF/MSVDhKrJykfIRAutQAJ4kOnOfH+zFPrcOccPqQrzyafMP8ACfXbu7
9sHpaM3kvFUv3MxBmYXWe8U=
=QJe/
-END PGP SIGNATURE-

-- 
MySQL Announce Mailing List
For list archives: http://lists.mysql.com/announce
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]



Timestamp issue

2002-09-17 Thread Prafulla Girgaonkar


Mysql Version::

Server version  3.23.47-nt
Protocol version10
Connection  . via named pipe
UNIX socket MySQL

OS::
Windows NT 4.0 Workstation


Hello
Following is the description of the problem being faced.

Problem:
The first timestamp column in a table is set to current date-time value as soon as we 
update one or more columns in the table.

Example:

The guest information is stored in a table named GUEST. The schema for it is as below.

create table guest (guestID int, arrivalDate timestamp, departureDate timestamp, 
status char(1));

Above table is populated using following queries.

insert into guest values (1, '2002-09-30',  '2002-10-14', 'Y');
insert into guest values (2, '2002-09-20',  '2002-10-01', 'Y');
insert into guest values (3, '2002-09-15',  '2002-09-25', 'Y');
insert into guest values (4, '2002-09-12',  '2002-09-20', 'Y');


If we use following query to update the status from Y to N, then arrivalDate column is 
set to CURRENT(system) date-time value.

update guest set status = 'N';

Does anybody have any information on this issue?

Thanx in advance.

Prafulla

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Timestamp issue in mysql

2002-09-17 Thread Prafulla Girgaonkar

Hello
Following is the description of the problem being faced.

Problem:
The first timestamp column in a table is set to current date-time value as soon as we 
update one or more columns in the table.

Example:

The guest information is stored in a table named GUEST. The schema for it is as below.

create table guest (guestID int, arrivalDate timestamp, departureDate timestamp, 
status char(1));

Above table is populated using following queries.

insert into guest values (1, '2002-09-30',  '2002-10-14', 'Y');
insert into guest values (2, '2002-09-20',  '2002-10-01', 'Y');
insert into guest values (3, '2002-09-15',  '2002-09-25', 'Y');
insert into guest values (4, '2002-09-12',  '2002-09-20', 'Y');


If we use following query to update the status from Y to N, then arrivalDate column is 
set to CURRENT(system) date-time value.

update guest set status = 'N';

Does anybody have any information on this issue?

Thanx in advance.

Prafulla

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php