14 May
2013
14 May
'13
2:24 a.m.
There were a couple of things that i wanted to know
1) I was going through the this feature request
https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
and i too wasn't able to figure out how to change database name. Has that
feature been implemented
2) while exporting the database there is no create database sql statement
for example :
there is a db called test with certain number of tables. I selected the
database, clicked on export, clicked custom and exported it.
However only the tables were exported. There were no create statement
Shouldn't the entire database be exported with create database statement?
Is this a bug or was this not implemented intentionally
15 May
15 May
2:07 a.m.
Le 2013-05-13 19:24, ayush choubey a écrit :
There were a couple of things that i wanted to know
1) I was going through the this feature request
https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
and i too wasn't able to figure out how to change database name. Has
that feature been implemented
Click on the database, then Operations. You'll find a dialog to rename
the database.
2) while exporting the database there is no create database sql statement
for example :
there is a db called test with certain number of tables. I selected the
database, clicked on export, clicked custom and exported it.
However only the tables were exported. There were no create statement
Shouldn't the entire database be exported with create database
statement? Is this a bug or was this not implemented intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
--
Marc Delisle
http://infomarc.info
3:12 a.m.
On Wed, May 15, 2013 at 4:37 AM, Marc Delisle <marc(a)infomarc.info> wrote:
We have hierarchy in this fashion
Server->Database->tables
Now when we have to export a table, we click on export and we expect that
there will
be a CREATE TABLE statement and INSERT statement
But when we have to export a server there are just CREATE TABLE statements
and
INSERT STATEMENTS.
So, in case the user wants to export a DB named test and his target machine
has no test.
In this case he would like sql file to have CREATE DATABASE test followed
by tables
To achieve this he will have to go to :
server level -> click on export->select custom->select test-> export->Go
If we add one CREATE DATABASE IF NOT EXISTS at database export level, then
his steps would be
Select test->export->Go
Le 2013-05-13 19:24, ayush choubey a écrit :
Well, i was thinking of adding a "export as" feature there for this Feature
request
that will take a name and thus generated sql file will have that exported
database name.
But i guess renaming it is better option.
There were a couple of things that i wanted to
know
1) I was going through the this feature request
https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
and i too wasn't able to figure out how to change database name. Has
that feature been implemented
Click on the database, then Operations. You'll find a dialog to rename
the database.
2) while exporting the database there is no
create database sql statement
for example :
there is a db called test with certain number of tables. I selected the
database, clicked on export, clicked custom and exported it.
However only the tables were exported. There were no create statement
Shouldn't the entire database be exported with create database
statement? Is this a bug or was this not implemented intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
From the user point of view, i guess, this will be much
more preferred as
it has less number
of steps.
--
Marc Delisle
http://infomarc.info
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
16 May
16 May
1:39 p.m.
Le 2013-05-14 20:12, ayush choubey a écrit :
On Wed, May 15, 2013 at 4:37 AM, Marc Delisle <marc(a)infomarc.info
<mailto:marc@infomarc.info>> wrote:
Le 2013-05-13 19:24, ayush choubey a écrit :
You probably meant "when we have to export a database" ?
There were a couple of things that i wanted to
know
1) I was going through the this feature request
https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
and i too wasn't able to figure out how to change database name. Has
that feature been implemented
Click on the database, then Operations. You'll find a dialog to rename
the database.
Well, i was thinking of adding a "export as" feature there for this
Feature request
that will take a name and thus generated sql file will have that
exported database name.
But i guess renaming it is better option.
2) while exporting the database there is no create database sql
statement
for example :
there is a db called test with certain number of tables. I
selected the
database, clicked on export, clicked custom and
exported it.
However only the tables were exported. There were no create statement
Shouldn't the entire database be exported with create database
statement? Is this a bug or was this not implemented intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
We have hierarchy in this fashion
Server->Database->tables
Now when we have to export a table, we click on export and we expect
that there will
be a CREATE TABLE statement and INSERT statement
But when we have to export a server there are just CREATE TABLE
statements and
INSERT STATEMENTS.
So, in case the user wants to export a DB named test and his target
machine has no test.
In this case he would like sql file to have CREATE DATABASE test
followed by tables
To achieve this he will have to go to :
server level -> click on export->select custom->select test-> export->Go
If we add one CREATE DATABASE IF NOT EXISTS at database export level, then
his steps would be
Select test->export->Go
From the user point of view, i guess, this will be much
more preferred as it has less number
of steps.
--
Marc Delisle
http://infomarc.info
2:59 p.m.
On Thu, May 16, 2013 at 4:09 PM, Marc Delisle <marc(a)infomarc.info> wrote:
Le 2013-05-14 20:12, ayush choubey a écrit :
rename
You probably meant "when we have to export a database" ?
Oh, yeah, sorry, i meant Database, by mistake i wrote it as server.
On Wed, May 15, 2013 at 4:37 AM, Marc Delisle <marc(a)infomarc.info
<mailto:marc@infomarc.info>> wrote:
Le 2013-05-13 19:24, ayush choubey a écrit :
> There were a couple of things that i wanted to know
>
> 1) I was going through the this feature request
> https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
>
> and i too wasn't able to figure out how to change database name.
Has
that
feature been implemented
Click on the database, then Operations. You'll find a dialog to the database.
Well, i was thinking of adding a "export as" feature there for this
Feature request
that will take a name and thus generated sql file will have that
exported database name.
But i guess renaming it is better option.
statement
2) while exporting the database there is no create database sql
statement
for example :
there is a db called test with certain number of tables. I
selected the
> database, clicked on export, clicked custom and exported it.
>
> However only the tables were exported. There were no create
Shouldn't the entire database be exported with create database
statement? Is this a bug or was this not implemented intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
We have hierarchy in this fashion
Server->Database->tables
Now when we have to export a table, we click on export and we expect
that there will
be a CREATE TABLE statement and INSERT statement
But when we have to export a server there are just CREATE TABLE
statements and
INSERT STATEMENTS.
So, in case the user wants to export a DB named test and his target
machine has no test.
In this case he would like sql file to have CREATE DATABASE test
followed by tables
To achieve this he will have to go to :
server level -> click on export->select custom->select test-> export->Go
If we add one CREATE DATABASE IF NOT EXISTS at database export level,
then
his steps would be
Select test->export->Go
From the user point of view, i guess, this will be much
more preferred as it has less number
of steps.
--
Marc Delisle
http://infomarc.info
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
3:32 p.m.
ayush choubey a écrit :
On Thu, May 16, 2013 at 4:09 PM, Marc Delisle
<marc(a)infomarc.info> wrote:
You could add a CREATE DATABASE IF NOT EXISTS statement when exporting
at the database level.
Le 2013-05-14 20:12, ayush choubey a écrit :
rename
You probably meant "when we have to export a
database" ?
Oh, yeah, sorry, i meant Database, by mistake i wrote it as server.
On Wed, May 15, 2013 at 4:37 AM, Marc Delisle <marc(a)infomarc.info
<mailto:marc@infomarc.info>> wrote:
Le 2013-05-13 19:24, ayush choubey a écrit :
> There were a couple of things that i wanted to know
>
> 1) I was going through the this feature request
> https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
>
> and i too wasn't able to figure out how to change database name.
Has
that
feature been implemented
Click on the database, then Operations. You'll find a dialog to the database.
Well, i was thinking of adding a "export as" feature there for this
Feature request
that will take a name and thus generated sql file will have that
exported database name.
But i guess renaming it is better option.
statement
2) while exporting the database there is no create database sql
statement
for example :
there is a db called test with certain number of tables. I
selected the
> database, clicked on export, clicked custom and exported it.
>
> However only the tables were exported. There were no create
Shouldn't the entire database be exported with create database
statement? Is this a bug or was this not implemented intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
We have hierarchy in this fashion
Server->Database->tables
Now when we have to export a table, we click on export and we expect
that there will
be a CREATE TABLE statement and INSERT statement
But when we have to export a server there are just CREATE TABLE
statements and
INSERT STATEMENTS.
>> So, in case the user wants to export a DB named test and his target
>> machine has no test.
>> In this case he would like sql file to have CREATE DATABASE test
>> followed by tables
>>
>> To achieve this he will have to go to :
>>
>> server level -> click on export->select custom->select test->
export->Go
>>
>> If we add one CREATE DATABASE IF NOT EXISTS at database export level,
> then
>> his steps would be
>> Select test->export->Go
>> From the user point of view, i guess, this will be much
>> more preferred as it has less number
>> of steps.
> --
> Marc Delisle
> http://infomarc.info
--
Marc Delisle
http://infomarc.info
7 p.m.
Sure sir,
I have sent a pull request regarding this
https://github.com/phpmyadmin/phpmyadmin/pull/395
Please have a look at it.
Thank you
On Thu, May 16, 2013 at 6:02 PM, Marc Delisle <marc(a)infomarc.info> wrote:
ayush choubey a écrit :
Oh, yeah, sorry, i meant Database, by mistake i wrote it as server.
You could add a CREATE DATABASE IF NOT EXISTS statement when exporting
at the database level.
On Thu, May 16, 2013 at 4:09 PM, Marc Delisle
<marc(a)infomarc.info>
wrote:
> Le 2013-05-14 20:12, ayush choubey a écrit :
>>
>>
>> On Wed, May 15, 2013 at 4:37 AM, Marc Delisle <marc(a)infomarc.info
>> <mailto:marc@infomarc.info>> wrote:
>>
>> Le 2013-05-13 19:24, ayush choubey a écrit :
>> > There were a couple of things that i wanted to know
>> >
>> > 1) I was going through the this feature request
>> > https://sourceforge.net/p/phpmyadmin/feature-requests/1387/
>> >
>> > and i too wasn't able to figure out how to change database name.
> Has
>> > that feature been implemented
>>
>> Click on the database, then Operations. You'll find a dialog to
> rename
>> the database.
>>
>> Well, i was thinking of adding a "export as" feature there for this
>> Feature request
>> that will take a name and thus generated sql file will have that
>> exported database name.
>> But i guess renaming it is better option.
>>
>>
>> >
>> > 2) while exporting the database there is no create database sql
>> statement
>> >
>> > for example :
>> >
>> > there is a db called test with certain number of tables. I
>> selected the
>> > database, clicked on export, clicked custom and exported it.
>> >
>> > However only the tables were exported. There were no create
> statement
>> >
>> > Shouldn't the entire database be exported with create database
>> > statement? Is this a bug or was this not implemented
intentionally
I guess nobody ever felt the need for this. The CREATE DATABASE
statement is generated when you export at the server level.
We have hierarchy in this fashion
Server->Database->tables
Now when we have to export a table, we click on export and we expect
that there will
be a CREATE TABLE statement and INSERT statement
But when we have to export a server there are just CREATE TABLE
statements and
INSERT STATEMENTS.
You probably meant "when we have to export a
database" ?
>> So, in case the user wants to export a DB named test and his target
>> machine has no test.
>> In this case he would like sql file to have CREATE DATABASE test
>> followed by tables
>>
>> To achieve this he will have to go to :
>>
>> server level -> click on export->select custom->select test->
export->Go
>>
>> If we add one CREATE DATABASE IF NOT EXISTS at database export level,
> then
>> his steps would be
>> Select test->export->Go
>> From the user point of view, i guess, this will be much
>> more preferred as it has less number
>> of steps.
> --
> Marc Delisle
> http://infomarc.info
--
Marc Delisle
http://infomarc.info
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Phpmyadmin-devel mailing list
Phpmyadmin-devel(a)lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/phpmyadmin-devel
4144
days inactive
4147
days old
6 comments
2 participants
participants (2)
-
ayush choubey -
Marc Delisle