Hi,
I would like to know how to make the label of the checkbox appear next to it,
and not under it. This is on the table structure editing page.
The following code appears on one HTML line.
Thanks,
Marc
<td bgcolor="#E5E5E5" align="center">
<input type="hidden" name="field_default_orig[]" size="8" value="CURRENT_TIMESTAMP" /><input
id="field_0_7" type="text" name="field_default[]" size="12" value="" class="textfield" /><br
/><input id="field_0_7a" type="checkbox" name="field_default_current_timestamp[0]" checked="checked"
/><label for="field_0_7a" style="font-size: x-small;">CURRENT_TIMESTAMP</label></td>
_ __ __ _ _ _
_ __ | |__ _ __ | \/ |_ _ / \ __| |_ __ ___ (_)_ __
| "_ \| "_ \| "_ \| |\/| | | | | / _ \ / _` | "_ ` _ \| | "_ \
| |_) | | | | |_) | | | | |_| |/ ___ \ (_| | | | | | | | | | |
| .__/|_| |_| .__/|_| |_|\__, /_/ \_\__,_|_| |_| |_|_|_| |_|
|_| |_| |___/ 2.6.2-beta1
http://www.phpmyadmin.net
phpMyAdmin 2.6.2-beta1 - March 27th, 2005
=========================================
A set of PHP-scripts to administrate MySQL over the Web.
--------------------------------------------------------
Announcement
------------
The phpMyAdmin Project is proud to announce the immediate
availability of the first beta release of phpMyAdmin 2.6.2.
Version 2.6.2 contains improvements for better MySQL 4.1 and 5.0
support.
phpMyAdmin is a web administration tool for MySQL databases, intended to
handle a whole database server as well as a single database. Over the years,
it has become the most popular GUI for MySQL and is downloaded about 6,000
times a day, according to SourceForge.net.
The highlights of this release in detail:
Highlights
----------
Improvements:
* MySQL 4.1.x native column comments
* MySQL 5.0: Basic detection mechanism for views:
o Views are no longer displayed as tables in use
o Ability to drop views
* MySQL 5.0: Interface fixes and hardcoded virtual relations for information_schema
* MySQL 4.1: Better automatic detection for available storage engines
* New storage engines overview page
o Plugin-like infrastructure for storage engine status monitors
o Overview of startup variables and current values
o MySQL 5.0 / InnoDB: Buffer pool activity monitor
* MySQL 4.1.2+ TIMESTAMP options: initial support when editing table structure
* Export: Native Microsoft Word 2000 and Excel 2000 formats
* PDF schema visual editor: column names now optional
* MySQL 5.0.3 new Japanese charsets support (cp932, eucjpms)
* Parser: added missing date and time MySQL functions
* Documentation: explain all Export options handling
* Cookie paths: added / to end of path
* Show database comments at more places
* Better use of print styles in themes
* Bookmarks: sort by label, remove the number before each label
* Better protection against possible collation conflicts and out-of-sync errors in PMADB queries
* Relation view: removed pmadb-style comments handling (now available just on the Structure page)
* FAQ about using HTTP authentication under IIS
* New editions for some language files (especially ISO-8859-15)
Fixes:
* Detection of SELECT query to display on multiple submits
* PDF schema: missing header
* A failed connection was not properly detected
* Problem with Japanese language under MySQL 4.1.x
* Export
o Various errors under mysqli extension
o SQL format under Safari browser
o Do not offer export modes not available in current MySQL version
* Changing the type of a FLOAT unsigned column
* Adding field with collation
* Calendar popup and TIMESTAMP field under MySQL 4.1.x
* PHP 4.1.x: wrong parameter count (mcrypt.lib.php)
* Problem when SHOW DATABASES is disabled
* Copy table: commands out of sync
* User management
o Host not changing with editing user
o Escaping character removed by error
* MySQL 5.0.x: "No database selected" error
* Print view: displaying of indexes
* Cookie auth: error when blowfish_secret is empty
* MySQL 4.1.2: "Reload MySQL" link not seen
* MySQL 5 server binlog compatibility
* PDF pages generation: wrong documentation
* Inserted row id was not always correctly reported
Detailed list of changes since version 2.2.0 is available under
http://www.phpmyadmin.net/ChangeLog.txt
Availability
------------
This software is available under the GNU General Public License V2.0.
You can get the newest version at http://www.phpmyadmin.net/
Available file formats are: .zip, .tar.gz and .tar.bz2.
If you install phpMyAdmin on your system, it"s recommended to
subscribe to the news mailing list by adding your address under
http://lists.sourceforge.net/lists/listinfo/phpmyadmin-news
This way, you will be informed of new updates and security fixes.
It is a read only list, and traffic is not greater than a few
mail every year.
Support and Documentation
-------------------------
The documentation is included in the software package as text and
HTML file, but can also be downloaded from:
http://www.phpmyadmin.net/documentation/
The software is provided as is without any express or implied
warranty, but there is a bugs tracker page under:
http://sourceforge.net/projects/phpmyadmin/ [click on "Bugs"]
In addition, there are also a number of discussion lists
related to phpMyAdmin. A list of mailing lists with archives
is available at:
http://sourceforge.net/mail/?group_id=23067 or
http://sourceforge.net/projects/phpmyadmin/ [click on "Lists"]
Finally, an users support forum is also available under:
http://sourceforge.net/forum/forum.php?forum_id=72909
Known bugs
----------
- phpMyAdmin SQL parser chokes on fieldnames with certain non-ASCII characters
(bugs #593598, #936161).
To be informed about new releases fixing these problems, please
subscribe to the news mailing list under
http://lists.sourceforge.net/lists/listinfo/phpmyadmin-news
or regularly check the sourceforge bugs tracker.
Donations
---------
The project accepts donations to help improve the product. There is
a "Donations" link on http://www.phpmyadmin.net.
Description
-----------
phpMyAdmin is intended to handle the administration of MySQL over the Web. It
can manage a whole MySQL server as well as a single database.
Currently it can:
- create, copy, rename and drop databases
- create, copy, drop, rename and alter tables
- do table maintenance
- delete, edit and add fields
- execute any SQL-statement, even batch-queries
- manage keys on fields
- load text files into tables
- create and read dumps of tables
- export data to CSV, XML and Latex formats
- administer multiple servers
- manage MySQL users and privileges
- check referential integrity
- using Query-by-example (QBE), create complex queries automatically
connecting required tables
- create PDF graphics of your Database layout
- search globally in a database or a subset of it
- communicate in 47 different languages
Authors & Copyright
-------------------
Copyright (C) 1998-2000 Tobias Ratschiller <tobias_at_ratschiller..com>
Copyright (C) 2001-2005 Marc Delisle <DelislMa_at_CollegeSherbrooke.qc.ca>
Olivier Müller <om_at_omnis.ch>
Robin Johnson <robbat2_at_users.sourceforge.net>
Alexander M. Turek <me_at_derrabus.de>
Michal Cihar <michal_at_cihar.com>
Garvin Hicking <me_at_supergarv.de>
Marcel Tschopp <ne0x_at_users.sourceforge..net>
+ many other people
(check the CREDITS section of our documentation)
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Marc Delisle/ 2005-03-27
Hi,
Due to the new "TIMESTAMP options" feature not completely implemented
yet, I will release today 2.6.2-beta1. This means a feature freeze,
except for completing the new feature this week. It should touch only 2
or 3 scripts. 2.6.2-rc1 should follow one week later.
I suggest creating the 2.6.2 branch only when -rc1 is released, unless
someone has an urgent need for starting 2.6.3.
Another point for those who are not following sf.net upgrades; they
mention this:
"MySQL database version upgrade, centralized phpMyAdmin:
MySQL database services will be upgraded to MySQL
4.0.x. At that time, we will begin offering a
centralized phpMyAdmin service, allowing projects to
more readily maintain their project database."
Marc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi devels,
As you have probably noticed, phpMyAdmin 2.6.2 at its current state
should be able to live with withs, which basically means that we still
treat them as tables, but they don't break our interface anymore.
For those of you, who don't know views yet (which would not be a big gap
in your knowlege as this feature does not exist in MySQL before 5.0):
A view is basically a derived table, based on a SELECT statement. That
means that I can take the result of a SELECT query and create a new
permanent virtual table from it. Of course, you can perform SELECTs on
it as if it was a real table and its content is always synchronized with
the underlying base tables. And the best is: you can grant privileges on
a view as if it was a table!
So back to topic: As I said, phpMyAdmin already detects existing views.
But it would be really fancy, if phpMyAdmin somehow could support the
user when it comes to create those views.
The obvious way would be to add a link "Create new view" and when
clicking it, displaying a big textarea where the user may enter his
SELECT statement. Wee. Easy to implement, but absolutely unexiting,
because for the user, it is equally complex to enter "CREATE VIEW `foo`
AS" plus his SELECT statement into a simple query box.
Generally, it is not a bad idea to test a query first before creating a
view from it - at least I do so. So when displaying a SELECT query,
maybe we should offer an option "Create view from query" that leads to a
page that allows me to give that view a name and maybe a comment and
ajust some settings for it.
Another way would be merging it with the export code: when clicking the
"Export" link in browse mode, we could offer to export the SELECT
statement as view.
Both solutions would allow us to combine the view creation with
phpMyAdmin's search feature or the QBE with automatic joins. The latter
could be turned into a powerful view editor this way!
Some other things, I thought about:
Maybe we can also merge it with the bookmarks code: Somehow, the
combination of stored procedures and views can be seen as MySQL's answer
to our bookmark system: SELECT statements can be "bookmarked" as views,
everything else as stored procedures. Nevertheless, those two don't
replace the bookmarks, as there may be users who are not allowed to
create either of them.
It is currently not possible to comment views (natively), neither a view
itself, nor its columns. And at least for the column level, I doubt that
they ever will be. Maybe, we could reactive our pmadb based column
comments code for this?
Views are currently not exportable in phpMyAdmin. But when creating a
database dump, a user might want to have the corresponding CREATE VIEW
statements included.
Using pmadb, it is possible to define foreign keys on views. Do you
think, that it is possible to have views "inheriting" their relations
from the corresponding base tables? This could be really useful,
especially because views _can_ be updatable under certain circumstances,
which basically means that you can insert into views or manipulate their
records directly. I know this sounds sick, but it really works! :o)
Detecting those updatable views will be easy as soon as the
information_schema database works without crashing mysqld (d'oh).
All this is just the result of not being able to sleep at 3 am. ;-)
I just wanted to get your comments about this and to check for
volunteers - especially for the view creation part. :-)
But I will probably also post this to the RFE tracker, soon.
Some literature about all this:
CREATE VIEW syntax:
http://dev.mysql.com/doc/mysql/en/create-view.html
About information_schema:
http://dev.mysql.com/doc/mysql/en/information-schema.html
About stored procedures:
http://dev.mysql.com/doc/mysql/en/stored-procedures.html
Regards,
AMT
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCLRlf8c/ssWf/SMcRAoJwAJ9v6FFFiG2GHTsO1zQp2A9oFwMX4ACggYj8
f/YDJ0wtgGQdRtXWJOTrxrQ=
=Iizh
-----END PGP SIGNATURE-----
Hi,
I just merged some changes to support table structure editing of MySQL
4.1.2+ TIMESTAMP options.
Currently, I add ON UPDATE CURRENT_TIMESTAMP into the list of attributes
for MySQL 4.1.2 (instead of doing it in config.inc.php, because
the config import does not deal with new items in an array, AFAIK).
Also, for a TIMESTAMP I added a checkbox and CURRENT_TIMESTAMP under the
default value.
Please someone tell me how to put the checkbox next to the label :)
You can have a try. Due to the MySQL behavior, funny things happen when
you deactivate those options for a field, or when you try to set them
for a TIMESTAMP which is not the first one.
If you are pleased with this, I will add the options also for table
creation and field addition. However, I think in this case I would
add the CURRENT_TIMESTAMP checkbox for all fields, because I don't yet
know if it's going to be a TIMESTAMP. Unless someone has a better idea :)
Marc
Hi all
I just added Excel and Word export heavily inspired by mantis
<http://www.mantisbt.org> code. However I could test it only in
OpenOffice.org, so it would be great if somebody could give some
testing in real Microsoft programs :-). It is expected to work in 2000
version and higher, it won't work in 97.
--
Michal Čihař | http://www.cihar.com
Hi,
Here is patch level 3 for phpMyAdmin 2.6.1. It fixes a problem
introduced in -pl2: can no longer update a field whose name starts with
"str".
Also included, a fix for the privileges management module: escaping of
the "_" character was not properly done, giving a wildcard privilege
when editing db-specific privileges with phpMyAdmin.
Details at http://www.phpmyadmin.net
Marc Delisle, for the team
