Menu

#1603 (ok 4.5) select structure or structure+data for each table when exporting entire database

Next_release
resolved
None
Low
2015-06-27
2015-02-04
FreeYUM!
No

(For GSoC 2015)

I ask, if possible, when I export an entire database,
select for each table to export only the structure or structure and data.

usually I happen to copy an entire structure when I start a new project, but data from some tables (log, references, who is online, and so on) do not interest me, and increase the size of the export exaggerated!

thank you!

Discussion

  • Olaf van der Spek

    Can't you first export all structures and then export data of a few tables?

     
  • tapanhalani

    tapanhalani - 2015-03-12

    I have an idea about how could I implement this feature. I know this feature is reserved for GSOC 2015, but I would like to plan my each step well in advance.

    Should I write my implementation idea here? Or should I send it to the mentors personally?

    I would like your reviews regarding my ideas, as I have added this feature and its implementation details to my project proposal..

     
    • Marc Delisle

      Marc Delisle - 2015-03-13

      At this point, it's best to include the implementation details in your proposal, once you can send it to the Melange site.

       
  • tapanhalani

    tapanhalani - 2015-03-14

    Hello Marc,

    We currently have a select list for selecting a table to export while exporting complete db. Is is ok , if I change that to a scrollable table with 3 more columns, each having a single checkbox, showing:

    1- table is selected or not
    2- structure to be exported or not for that table.
    3- data to be exported or not for that table.

    This would give the user the flexibility to select what to export..

     
  • Aayush

    Aayush - 2015-03-23

    Please tell me if this feature is also desired when whole server is exported..?

     
    • Marc Delisle

      Marc Delisle - 2015-03-24

      I believe it would be enough to implement this at the db level only.

       
      • Isaac Bennetch

        Isaac Bennetch - 2015-03-24

        I agree with Marc here, this is probably not needed at the server level.

         
      • Aayush

        Aayush - 2015-03-24

        ok.. thanks..

         
  • Nisarg Jhaveri

    Nisarg Jhaveri - 2015-06-24

    I am planning to implement scroll-able list of tables with 3 checkboxes as Tapan suggested. Two, each one of them for data and structure and another one to easily select or deselect table and update the other two. Also, 3 more checkboxes (or maybe buttons?) to select/deselect all.

    Also, the current options for selecting structure, data or both will be removed and the config option for that will be used for default values of the checkboxes.

    Does it sound good? Suggestions?

     
    • Marc Delisle

      Marc Delisle - 2015-06-24

      Sounds good. When you say "update the other two", I guess the other two checkboxes for one table (data, structure) would be updated with the default value when the select/deselect table is ticked, and would be cleared when it's unticked?

       
      • Nisarg Jhaveri

        Nisarg Jhaveri - 2015-06-24

        Yes.

         
    • Nisarg Jhaveri

      Nisarg Jhaveri - 2015-06-24

      The config option for data or structure is export plugin specific and some of them don't even support this. With the proposed structure, we select export plugin after selecting table wise structure or data. How do we manage this? Any ideas?

       
      • Marc Delisle

        Marc Delisle - 2015-06-24

        I haven't looked at the code, but here is a UI suggestion. For any export format, the table selection can be done with checkboxes instead of the current multiple selector. Then, depending on the format chosen, the additional checkboxes can be shown/hidden.

         
  • Marc Delisle

    Marc Delisle - 2015-06-27
    • summary: select structure or structure+data for each table when exporting entire database --> (ok 4.5) select structure or structure+data for each table when exporting entire database
    • status: open --> resolved
    • Priority: Normal --> Low