Ninad Pundalik a écrit :
> On 28 May 2010 22:19, Marc Delisle <marc@...> wrote:
>> your list is interesting and covers a lot of actions. I am not sure
>> about your intention for some actions. For example, the "copy database"
>> action; what's your plan? Will the user see a progress bar for the whole
>> operation? and/or see a display of the current table name being copied?
> Currently, when copying a database, a series of SQL queries is
> executed and then, the same page reloads, with the successful query
> shown on the page along with a message that the database has been
> copied. Keeping this in mind, my idea was to show the response
> (success/error) in either a dialog, or append it to the current page.
> If the user has requested to switch to the new database, then the page
> would be reloaded with the new database, otherwise, the user can carry
> on working with the current database. This is a very simple
> For a progress bar to be shown, we would have to break down this task
> into smaller steps (like Create db, Create tables, copy data into
> tables) and stream responses to the client/browser as each step is
> completed. Or, can this be done in a better way? I'll read up
> streaming HTTP responses if this is to be implemented.
It depends if we want a progress bar that increases more or less in a
linear way; probably not necessary in this situation, as counting the
number and size of records before the copy is too much overhead.
>> than the Search page, would it be possible to ajaxify the table Search
>> page instead? A behavior that annoys me (and surely others) is that the
> The search page uses sql.php to actually run the query, which I will
> be modifying for Ajax. So, it will not be very difficult to ajaxify
> the database and table search page. I've added it to the list of
> tasks. :)
OK, only if you have time.
> I've created a page on the phpMyAdmin wiki with the list of tasks (
> http://wiki.phpmyadmin.net/pma/AJAXify_Interface ). Please use this
> for further reference instead of the pastebin.