Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#20 Possibility to export result sets

open
nobody
None
5
2006-10-31
2002-05-16
Teemu Hänninen
No

I would like to have a possibility to export result
sets in csv (comma separated) format. Even the
possibility to save as fixed-width column text-file
would help.

Discussion

  • Colin Bell
    Colin Bell
    2002-05-17

    • assigned_to: nobody --> colbell
     
  • Colin Bell
    Colin Bell
    2002-05-17

    Logged In: YES
    user_id=233132

    This is being looked at for a future release. As a
    workaround if you right click in the Result set table you
    can copy and paste the results as both text and HTML.

    Col

     
  • Logged In: YES
    user_id=379231

    and you can export it as insert statements if you want. So
    that you have a dump of the a select statement (see session-
    >scripts->data from sql)

     
  • Colin Bell
    Colin Bell
    2002-09-23

    Logged In: YES
    user_id=233132

    From
    https://sourceforge.net/tracker/index.php?func=detail&aid=613320&group_id=28383&atid=393417

    Hi,

    We do tons of loading/unloading the tables to/from
    ASCII files. For backups, moving data around,
    processing, and many other cases. Some DB's have a
    utility to do this (like Sybase's BCP). Other have none
    and that's it. Like Oracle. I have searched the Internet
    back and forth and found only dump to an Oracle binary
    format, load-only utility w/o a matching unloading utility
    or PL/SQL scripts that would do this.

    A really usefull thing, for many people as I can judge
    from amount of questions on the newsgroups, would be
    an export/import via JDBC only. Simple format, tabs
    and cr[/lf]. Order of columns as the default order in the
    DB.

    Surely, an XML format would be good but that's a bigggg
    machinery and if I have to do mapping for every table I
    need to export, move around and import, that is an
    overkill.

    Squirell would gain a lot with an extension like this!

    Stan Berka
    Pope & Talbot

     
  • Mark Fortner
    Mark Fortner
    2003-04-02

    Logged In: YES
    user_id=84783

    I wonder if it would be worthwhile to implement this via the
    RowSet Writer interface. It would give you the ability to
    write the ResultSet out as XML (via the default
    WebRowSetWriter implementation), but you could also provide
    a VelocityRowSetWriter, that would allow you to specify a
    template to be used for generating different (non-XML
    exports). If you extend the WebRowSet implementation, you
    could also allow other people to supply a XSLT to be used to
    process the rowset before writing it out to a file. You
    would also be able to use the Apache POI library to handle
    exporting in Excel format.

     
  • Mark Fortner
    Mark Fortner
    2003-04-02

    Logged In: YES
    user_id=84783

    I wonder if it would be worthwhile to implement this via the
    RowSet Writer interface. It would give you the ability to
    write the ResultSet out as XML (via the default
    WebRowSetWriter implementation), but you could also provide
    a VelocityRowSetWriter, that would allow you to specify a
    template to be used for generating different (non-XML
    exports). If you extend the WebRowSet implementation, you
    could also allow other people to supply a XSLT to be used to
    process the rowset before writing it out to a file. You
    would also be able to use the Apache POI library to handle
    exporting in Excel format.

     
  • Mark Fortner
    Mark Fortner
    2003-04-03

    Logged In: YES
    user_id=84783

    I wonder if it would be worthwhile to implement this via the
    RowSet Writer interface. It would give you the ability to
    write the ResultSet out as XML (via the default
    WebRowSetWriter implementation), but you could also provide
    a VelocityRowSetWriter, that would allow you to specify a
    template to be used for generating different (non-XML
    exports). If you extend the WebRowSet implementation, you
    could also allow other people to supply a XSLT to be used to
    process the rowset before writing it out to a file. You
    would also be able to use the Apache POI library to handle
    exporting in Excel format.

     
  • Mark Fortner
    Mark Fortner
    2003-04-03

    Logged In: YES
    user_id=84783

    I wonder if it would be worthwhile to implement this via the
    RowSet Writer interface. It would give you the ability to
    write the ResultSet out as XML (via the default
    WebRowSetWriter implementation), but you could also provide
    a VelocityRowSetWriter, that would allow you to specify a
    template to be used for generating different (non-XML
    exports). If you extend the WebRowSet implementation, you
    could also allow other people to supply a XSLT to be used to
    process the rowset before writing it out to a file. You
    would also be able to use the Apache POI library to handle
    exporting in Excel format.

     
  • Colin Bell
    Colin Bell
    2003-05-28

    • assigned_to: colbell --> patrickconnors
     
  • Logged In: NO

    How about the possibility to export/import blob data/images?
    This would be a real handy feature..

     
  • Colin Bell
    Colin Bell
    2006-10-31

    • assigned_to: patrickconnors --> nobody