Menu

#1 Fixes for console sqldump-3.0b1 (including major bug)

open
nobody
None
8
2005-02-05
2005-02-05
No

2005-02-05 Paul Sokolovsky
<pfalcon@users.sourceforge.net>

* getpw.c: Make password input work
correctly (at least
with msvcrt.dll), before it required to press
Enter twice.

* sqldump.c: Introduce --add-delete option:
before INSERTing
data into table, DELETE everthing from it (user
story: you have schema
for your database, which includes table
creation, procedure creation,
and initial data insertion. You would like to
backup only data from it.
You find it hard to filter out initial data from
the backup, so instead
dump everything, but with --add-delete
option. Restore sequence will be as
follows: 1) run the schema; 2) run the data
backup.)

* sqldump.c: Don't output debug info unless
requested by #define DEBUG.

* sqldump.c: Fix major bug: all INSERT
statements had column list from the last
table processed (this bug was not present in
sqldumpw).

* sqlutil.c: Don't expect database to contain
any tables.

* sqlwrap.c: Don't bother to commit
transaction (GO) after each and every
statement - instead, commit only after chunks
of statements - greately improve
restore time.

Discussion

  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05

    The diff

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05
    • priority: 5 --> 2
     
  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05

    The ChangeLog

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05

    Precompiled binary with patch

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05
    • priority: 2 --> 8
     
  • Paul Sokolovsky

    Paul Sokolovsky - 2005-02-05

    Logged In: YES
    user_id=11970

    I'm attaching a binary built with this patch.

    WARNING: USE AT YOUR OWN RISK!

    Build with mingw32-gcc 2.95.

     
  • Benjamin Mayrargue

    Logged In: YES
    user_id=89104

    thansk !!
    are you aware of a .NET version of this utility ?

     
  • Benjamin Mayrargue

    Logged In: YES
    user_id=89104

    Another thing,
    I've added a "USE {database name}" command at the start of
    the generated SQL.

    Very useful to execute the .sql file using osql.

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.