Menu

#239 Allow users to export all results

SQuirreL
closed
nobody
None
5
2017-11-26
2007-04-28
tmuerell
No

The data export dialog should allow the user to export all results of an SQL query, not regarding the limit. There could be a limit check box in the data export dialog as well to control how much lines are exported.

Discussion

  • Scott Carr

    Scott Carr - 2007-07-17

    Logged In: YES
    user_id=414180
    Originator: NO

    Before you run the SQL, there is a Limit checkbox above the SQL edit area. If you uncheck this box, it removes the limit, and you can therefore export ALL rows.

    This seems to not be an issue. Unless of course, I am missing something.

     
  • Rob Manning

    Rob Manning - 2007-07-17

    Logged In: YES
    user_id=1287991
    Originator: NO

    If memory serves me, I think the issue was that large data sets couldn't be displayed ( or took a long time to be displayed ) in the results panel. So, if a user wants to export all of the results to a file, this should be more efficiently done if the results don't have to be displayed in the results panel first. Therefore, a query result can be limited in SQuirreL to 100 records, but the export could be configured to ignore that limit.

    Rob

     
  • Nobody/Anonymous

    Logged In: NO

    Having either this feature, or the ability to directly export to a file when running the initial query would be ideal. That way, when there is a need to dump all of the data from a query with millions of results, it can easily be done (and by doing it in a streaming fashion, it would not consume very much memory at all, just time and disk space).

     
  • Nobody/Anonymous

    Logged In: NO

    kevinscarr,

    It would be an issue if you have a large amount of records and when the buffer is overspent. Therefore it's not always possible to extract results displayed on the screen, but rather should allow an option to export the whole table regardless of the limits. Maybe right clicking on a table name from object tree, then have a 'export this table' option.

    This way the results needed not to be shown to the screen and thus will not have any buffer overflow problem.

     
  • Nobody/Anonymous

    when you write your SQL statement, you would be able to check (O Results to file).
    Then
    On check, you could enter the name of the output file and a new|append flag
    or
    On run, you could enter the parameters...

     
  • Mageddo

    Mageddo - 2017-11-23

    Before found this issue I opened that one
    and I am talking about that, is not a good experience to load all results (when it is about hundred of thousands or millions) in the GUI and then export it to the file. I think export it to file directly makes more sense

     
  • Gerd Wagner

    Gerd Wagner - 2017-11-26

    Closed because, as Mageddo noticed, is already implemented.

     
  • Gerd Wagner

    Gerd Wagner - 2017-11-26
    • status: open --> closed
    • Group: --> SQuirreL
     

Log in to post a comment.