SQL Anywhere Feedback - Another reason dbunload -e should work differently

Author

Another reason dbunload -e should work differently

Breck Carter [TeamSybase]

2005-07-19, 7:23 am

CREATE EXISTING TABLE statements generated by dbunload are often not
needed in the target database, and they often don't work at all when
the reload.sql is being run because the remote server is inaccessible
at that time.

The dbunload -e option seems a natural for this... sadly, -e seems to
have "interesting" side effects that completely change the behavior of
dbunload, thus rendering -e useless for my purposes.

IMO -e should just exclude the named tables and have no other effect.

Breck

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Pavel Karady

2006-01-04, 1:23 pm

I'm interested in the -e switch used with dbunload - could you please state
SOME interesting side effects? To let us, average developers, be aware of
something in advance, not only when it's late...

Pavel

"Breck Carter [TeamSybase]" < NOSPAM__bcarter@risi
ngroad.com> wrote in
message news:2mlpd1t8j3vb7qu
672jngltv217o6msgku@
4ax.com...
> CREATE EXISTING TABLE statements generated by dbunload are often not
> needed in the target database, and they often don't work at all when
> the reload.sql is being run because the remote server is inaccessible
> at that time.
>
> The dbunload -e option seems a natural for this... sadly, -e seems to
> have "interesting" side effects that completely change the behavior of
> dbunload, thus rendering -e useless for my purposes.
>
> IMO -e should just exclude the named tables and have no other effect.
>
> Breck
>
> --
> SQL Anywhere Studio 9 Developer's Guide
> Buy the book:
> http://www.amazon.com/exec/obidos/A...7/risingroad-20
> bcarter@risingroad.com
> RisingRoad SQL Anywhere and MobiLink Professional Services
> www.risingroad.com

Sponsored Links