MySqlTalk.com  

Go Back   MySqlTalk.com > MySQL > Documentation
Reload this Page 1.6.5 New Features Planned for the Mid-Term Future
User Name
Password
FAQ Members List Calendar Search Today's Posts Mark Forums Read


Reply
 
Thread Tools Search this Thread
Old 06-08-2004, 02:48 AM   #1
Administrator
Administrator
 
Join Date: Jun 2004
Posts: 383 Administrator is on a distinguished road
1.6.5 New Features Planned for the Mid-Term Future
From http://dev.mysql.com/doc/mysql/en/TODO_sometime.html

1.6.5 New Features Planned for the Mid-Term Future
  • Implement function: get_changed_tables(timeout,table1,table2,...).
  • Change reading through tables to use mmap() when possible. Now only compressed tables use mmap().
  • Make the automatic timestamp code nicer. Add timestamps to the update log with SET TIMESTAMP=val;.
  • Use read/write mutex in some places to get more speed.
  • Automatically close some tables if a table, temporary table, or temporary file gets error 23 (too many open files).
  • Better constant propagation. When an occurrence of col_name=n is found in an expression, for some constant n, replace other occurrences of col_name within the expression with n. Currently, this is done only for some simple cases.
  • Change all const expressions with calculated expressions if possible.
  • Optimize key = expression comparisons. At the moment, only key = column or key = constant comparisons are optimized.
  • Join some of the copy functions for nicer code.
  • Change `sql_yacc.yy' to an inline parser to reduce its size and get better error messages.
  • Change the parser to use only one rule per different number of arguments in function.
  • Use of full calculation names in the order part (for Access97).
  • MINUS, INTERSECT, and FULL OUTER JOIN. (Currently UNION [in 4.0] and LEFT|RIGHT OUTER JOIN are supported.)
  • Allow SQL_OPTION MAX_SELECT_TIME=val, for placing a time limit on a query.
  • Allow updates to be logged to a database.
  • Enhance LIMIT to allow retrieval of data from the end of a result set.
  • Alarm around client connect/read/write functions.
  • Please note the changes to mysqld_safe: According to FSSTND (which Debian tries to follow), PID files should go into `/var/run/<progname>.pid' and log files into `/var/log'. It would be nice if you could put the "DATADIR" in the first declaration of "pidfile" and "log" so that the placement of these files can be changed with a single statement.
  • Allow a client to request logging.
  • Allow the LOAD DATA INFILE statement to read files that have been compressed with gzip.
  • Fix sorting and grouping of BLOB columns (partly solved now).
  • Change to use semaphores when counting threads. One should first implement a semaphore library for MIT-pthreads.
  • Add full support for JOIN with parentheses.
  • As an alternative to the one-thread-per-connection model, manage a pool of threads to handle queries.
  • Allow GET_LOCK() to obtain more than one lock. When doing this, it is also necessary to handle the possible deadlocks this change will introduce.
DISCUSS:
Administrator is offline   Fork this post Reply With Quote
Reply

« Previous Thread | Next Thread »

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
1.6.4 New Features Planned for the Near Future Administrator Documentation 0 06-08-2004 02:47 AM
1.6.3 New Features Planned for 5.1 Administrator Documentation 0 06-08-2004 02:46 AM
1.6.2 New Features Planned for 5.0 Administrator Documentation 0 06-08-2004 02:45 AM
1.6.1 New Features Planned for 4.1 Administrator Documentation 0 06-08-2004 02:45 AM
1.5.2.1 Features Available in MySQL 4.1 Administrator Documentation 0 06-08-2004 02:40 AM



All times are GMT -4. The time now is 01:23 PM.

Contact Us - MySqlTalk - Archive - TechTutorials - MySQL - Navicat - PHP - LinuxFund - Perl - Top


Powered by: vBulletin, Copyright ©2000 - 2008, Jelsoft Enterprises Limited.
Google
  Web http://www.mysqltalk.com
DISCLAIMERS:
1. We have no commercial interest in this site.
Banner Ads and Subscriptions will only be used to help pay for hosting and maintenance costs.
2. MySQLTalk.com is NOT affiliated with MySQL AB in any way.
3. MySQLTalk.com is NOT endorsed by MySQL AB in any way.
4. Please do not post any content that is harmful to MySQL or MySQL AB, meaning no misleading or obsolete information will be tolerated.
Well-founded constructive criticism meant to help the community is permitted.
5. This website is founded with the goal of improving the MySQL community.
We not only tolerate newbies, we encourage them.
Please do not ask newbies to "read the manual".