I have already implement it (3 lines : >).
From the edit page, now we can insert the data
as a new row as well. I reuse the string $strInsertNewRow. Wonder if I should add a new string $strSaveAndInsert instead..
What do you think?
Korakot
__________________________________________________ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
On Sun, May 06, 2001 at 01:34:35AM -0700, Korakot Chaovavanich wrote:
I have already implement it (3 lines : >). From the edit page, now we can insert the data as a new row as well.
great, thanks :) Another usefull function would be a "save and re-use" or "save and clone" : it would save the edited data, and directely open an insert form, but filled with same same data (maybe without filling the auto_increment field if any?).
And this "clone" link could also be placed at the side of the already existing "Edit" and "Delete" on the browse table view: that would be perfect for example while editing the user table from db mysql, to add another user with the same privilieges as another one.
Do you see what I mean ? I'll have some exams the following days, not time to work on it yet, but I guess it's also not very complicated.
I reuse the string $strInsertNewRow. Wonder if I should add a new string $strSaveAndInsert instead.. What do you think?
Yes, that would be usefull... you can than also directely add the $strSaveAndClone :)
Have a nice sunday, Olivier
On Sun, May 06, 2001 at 01:34:35AM -0700, Korakot Chaovavanich wrote:
I have already implement it (3 lines : >).
mmm, have you tested it ? :) Parse error: parse error in /home/admin/www/phpMyAdmin/tbl_replace.php3 on line 56
(using cvs version)
Oli
On Sun, May 06, 2001 at 11:46:30AM +0200, Olivier M. wrote:
On Sun, May 06, 2001 at 01:34:35AM -0700, Korakot Chaovavanich wrote:
I have already implement it (3 lines : >).
mmm, have you tested it ? :) Parse error: parse error in /home/admin/www/phpMyAdmin/tbl_replace.php3 on line 56 (using cvs version)
ok, a "{" were missing on line 19, but then the "new feature" still doesn't seem to work (both buttuns returns to the same place).
O.
Hi,
I would like to know what is the purpose of this new button...
Marc (Lem9)
"Olivier M." a écrit :
On Sun, May 06, 2001 at 11:46:30AM +0200, Olivier M. wrote:
On Sun, May 06, 2001 at 01:34:35AM -0700, Korakot Chaovavanich wrote:
I have already implement it (3 lines : >).
mmm, have you tested it ? :) Parse error: parse error in /home/admin/www/phpMyAdmin/tbl_replace.php3 on line 56 (using cvs version)
ok, a "{" were missing on line 19, but then the "new feature" still doesn't seem to work (both buttuns returns to the same place).
O.
Olivier Mueller - om@8304.ch - PGPkeyID: 0E84D2EA - Switzerland qmail projects: http://omail.omnis.ch - http://webmail.omnis.ch
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On Tue, May 08, 2001 at 09:51:03AM -0400, Marc Delisle wrote:
Hi, I would like to know what is the purpose of this new button...
me too... seems to do exactely the same as the other one. The goal (in my mind) was to be able to add/edit a row, and to diplay a new row form without having to go back to the table view.
Olivier
Ok, for a table without a primary key, you edit a record, then click "Insert new row", a new record will be inserted, instead of replacing the edited record.
If you click "save", this record is updated.
Marc (Lem9)
"Olivier M." a écrit :
On Tue, May 08, 2001 at 09:51:03AM -0400, Marc Delisle wrote:
Hi, I would like to know what is the purpose of this new button...
me too... seems to do exactely the same as the other one. The goal (in my mind) was to be able to add/edit a row, and to diplay a new row form without having to go back to the table view.
Olivier
On Tue, May 08, 2001 at 10:56:35AM -0400, Marc Delisle wrote:
Ok, for a table without a primary key, you edit a record, then click "Insert new row", a new record will be inserted, instead of replacing the edited record.
If you click "save", this record is updated.
ah ok, it is an "save as a new record", I see. Could be usefull, but won't help if you have 10 records to add, for example: there will be 20 requests (10x form, 10x table view). It would be nice (IMHO of course :) to have table view -> 10x form -> table view.
Olivier
"Olivier M." a écrit :
On Tue, May 08, 2001 at 10:56:35AM -0400, Marc Delisle wrote:
Ok, for a table without a primary key, you edit a record, then click "Insert new row", a new record will be inserted, instead of replacing the edited record.
If you click "save", this record is updated.
ah ok, it is an "save as a new record", I see. Could be usefull, but won't help if you have 10 records to add, for example: there will be 20 requests (10x form, 10x table view). It would be nice (IMHO of course :) to have table view -> 10x form -> table view.
It would be better to name the "insert new row" -> "insert as new row".
And a radio button: O go back to browse X continue inserting
Marc Delisle a écrit :
"Olivier M." a écrit :
On Tue, May 08, 2001 at 10:56:35AM -0400, Marc Delisle wrote:
Ok, for a table without a primary key, you edit a record, then click "Insert new row", a new record will be inserted, instead of replacing the edited record.
If you click "save", this record is updated.
ah ok, it is an "save as a new record", I see. Could be usefull, but won't help if you have 10 records to add, for example: there will be 20 requests (10x form, 10x table view). It would be nice (IMHO of course :) to have table view -> 10x form -> table view.
It would be better to name the "insert new row" -> "insert as new row".
And a radio button: O go back to browse X continue inserting
Oh yes, you wanted clone inserting, so:
O go back to browse X continue inserting (new data) O continue inserting (clone last data)
On Tue, May 08, 2001 at 11:33:13AM -0400, Marc Delisle wrote:
It would be better to name the "insert new row" -> "insert as new row".
And a radio button: O go back to browse X continue inserting
Oh yes, you wanted clone inserting, so:
O go back to browse X continue inserting (new data) O continue inserting (clone last data)
sounds great, right :)
Another little question: is there any way to delete/edit a bookmark? (on -devel version)
Olivier
Hi :)
A few days ago ;) Olivier wrote:
Another little question: is there any way to delete/edit a bookmark? (on -devel version)
Not really. Only by editing the bookmark table by...phpMyAdmin himself. I am not sure that it is necessary to see more complicated ?
Now, i'm working on the Tracker - Feature Request ID #422425.
Regards,
Armel.
Oops,
Somebody is working on the Tracker - Feature Request ID #420812 (GZIP of the DUMP) ? I am volunteer to work on it, if you want :) But i'm not sure that this feature will work without PHP4.0.4 and the gzencode() support. Any idea ?
Armel
Maybe execute gzip via system() or a similar call? Maybe too dependent on running under Unix?
Armel FAUVEAU a écrit :
Oops,
Somebody is working on the Tracker - Feature Request ID #420812 (GZIP of the DUMP) ? I am volunteer to work on it, if you want :) But i'm not sure that this feature will work without PHP4.0.4 and the gzencode() support. Any idea ?
Armel
Phpmyadmin-devel mailing list Phpmyadmin-devel@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
On Thu, May 10, 2001 at 01:20:41AM +0200, Armel FAUVEAU wrote:
Hi :)
A few days ago ;) Olivier wrote:
Another little question: is there any way to delete/edit a bookmark? (on -devel version)
Not really. Only by editing the bookmark table by...phpMyAdmin himself. I am not sure that it is necessary to see more complicated ?
Well, if you can create bookmarks, I think it should be possible to at least delete some when you don't need them anymore. Could be as easy as adding a [delete] button at the side of the load bookmark... Comments ? :)
Olivier
Hello,
Well, if you can create bookmarks, I think it should be possible to at least delete some when you don't need them anymore. Could be as easy as adding a [delete] button at the side of the load bookmark... Comments ? :)
Ok. I added this feature to the current-devel tree :)
Armel.
-
Armel FAUVEAU -
Korakot Chaovavanich -
Marc Delisle -
Marc Delisle -
Olivier M.