[arkid77]

Thanks so much Sathish for the reply. I have one more request… again something that can't be very time consuming at all to implement and would be very useful in some occasions.

Basically the ability for the “Tools/Execute External Script” feature to be able to batch run over multiple sql files. Why is this so useful? Well the sql export powertool lets you export to multiple sql files during backups. This is often desirable for servers with many databases when a full server backup was setup/scheduled.

Currently there is no way fo re-importing all those sql files at once. Like a few things with the program, there are not quite equal features on both sides of export/import functionality. It seems odd to me that you can do something as simple as export to multiple files without any way to then use sqlyog to use them again later for importing in any convenient way. Sure you can import them, just one at a time and its simply not practical in many situations.

Currently I have to use software from your competitors to do such a task.

Thanks

[arkid77]

Hi webyog…. was there any feedback on this request?

'arkid77' wrote:

Hi Peter

Yes in that kind of functionality but vitally, not there in the object browser but the create/modify interface.

This is handled very well in the Firefox browser.

To that end, Ive gone to the effort to make you an illustration.

Thanks

Adam

[arkid77]

Hi

Ah ok great, thank you. I dont have above 8.6.

Is access to it also available in right click context menus and database menu?

[arkid77]

'peterlaursen' wrote:

Even though details of implementation differ, I think this is something similar?

http://code.google.com/p/sqlyog/issues/detail?id=1119

Hi Peter

Yes in that kind of functionality but vitally, not there in the object browser but the create/modify interface.

This is handled very well in the Firefox browser.

To that end, Ive gone to the effort to make you an illustration.

Thanks

Adam

[arkid77]

'vishal.pr' wrote:

@arkid77

The mapping section will always show the column length and other properties of the column given in the source no matter whether you have selected to import into an existing table. Importing into existing table will never modify the target table structure even though mapping section shows otherwise, these values will have effect only if you drop and recreate the table.

FYI: Import into existing table is controlled by the DDL/DML Optionsin the Advanced Options.

Regards,

Vishal P.R

Hi Vishal

I would suggest that this interface be improved if possible as its quite confusing currently.

The most confusing part is that the drop down lists in the map page didnt even include the columns in my underlying database due to them not matching the eact same len value as the source. So even if it works if you manually type them, the fact you have to do that is very unfriendly and confusing. This to me seems to be the most key thing that could be improved.

Thanks

[arkid77]

'peterlaursen' wrote:

Could you please share a small Excel file and a SHOW CREATE TABLE output that demonstrates this problem?

Hi Peter

As requested…

CREATE TABLE `heathrow` (

`id` int(255) NOT NULL AUTO_INCREMENT,

`postcode` varchar(5) DEFAULT NULL,

`price` decimal(5,2) DEFAULT NULL,

PRIMARY KEY (`id`)

) ENGINE=InnoDB AUTO_INCREMENT=139 DEFAULT CHARSET=utf8

[arkid77]

'peterlaursen' wrote:

As regards the 'bug'. What we display is what the 'Windows Scheduler' returns. I am not able to explain why it return an American date format on you system with UK-English settings.

Could you please check the Windows Scheduler on your system? And are you sure that you have UK LOCALE and not only LANGUAGE?

Hi

Yes, these are definitely standard uk settings im running. Its a windows 7 system btw.

[arkid77]

Re my “bug”: I agree this is indeed a small point. However as a uk user I must say that when I think about it , i cant even remember the last time I saw a windows program showing me the date in the “wrong” US format. So its very rare for programs to not do some kind of detection/conversion. When the day of the month is less than 12 it is naturally very confusing and months and days of month can be read and assumed to be in uk format when not. I would expect any pro program to handle basic internationalisation such as this.

1) This sounds the same request as you mention. Yes I see youve a few fixed size windows and I understand some like wizzards must be a pain to change. However I guess this isnt the case here and would be great if it can be done or at least made bigger as an intermediary step.

2) It was just to have more columns inside this window (assuming the window is larger/redesigned/resizable). So it was to just state where the export is maybe being saved to, where the config xml is. Things like that. I had these questions in my mind as soon as I came to this window and wanted to check on the backup jobs I had made 6 months earlier. Off hand I had no memory of where they were being saved on my disk and this core information would be great if its in that window. As it stands, its quite fiddly to obtain this information because as i wrote, you have to edit the windows schedule task, extract the HUGE string from it (or at least it is when you save files in a medium sized folder path) and then read it in something like a text editor to work out what its doing.

3) I think you may misunderstand this request slightly. It was simply to allow quick access to edit an existing job, via your existing gui. So this edit job button would just launch the “scheduled backup job” wizzard and parse the xml file to it and launch it in edit mode. So this is exactly the same as manually closing this window, launching the wizard, selecting EDIT and then browsing to the xml job file. It was just a way to make this much quicker and this function screamed out at me because when troubleshooting existing jobs editing, ror at least viewing the existing job settings was what I realised I needed to do.

[arkid77]

Rohit wrote on Feb 5 2009, 04:26 PM:

It shouldn't be very tough. We will implement this but not high priority.

Thanks , this would really be great.

[arkid77]

the problem seems irelivent to my upgraded database. ive just created a new database via sqlyog on my 5.0.16 mysql server. i called the database test-dev. i then created a table with a simple field names without odd characters or anything unstandard. i went to the export option in sqlyog and again i got this error.

[Author]

Posts