Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM Enhancement Requests and Suggestions » View Thread |
Messages 1 to 5 of 5 total |
EDBMgr - Change Database Directory |
Thu, Sep 20 2007 11:51 AM | Permanent Link |
Dave Harrison | It seems odd that I can't change the database directory for an existing
database. I may want to copy the database to another drive (because I ran out of disk space) but the EDBMgr forces me to drop the old database and create a new database. Wouldn't it be easier if I could just edit the database property and modify the database directory? Dave |
Thu, Sep 20 2007 2:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Dave,
<< It seems odd that I can't change the database directory for an existing database. I may want to copy the database to another drive (because I ran out of disk space) but the EDBMgr forces me to drop the old database and create a new database. Wouldn't it be easier if I could just edit the database property and modify the database directory? >> 1.06 will have expanded ALTER capabilities for all ALTER statements, including the ALTER DATABASE statement. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Sep 20 2007 9:38 PM | Permanent Link |
Dave Harrison | Tim Young [Elevate Software] wrote:
> Dave, > > << It seems odd that I can't change the database directory for an existing > database. I may want to copy the database to another drive (because I ran > out of disk space) but the EDBMgr forces me to drop the old database and > create a new database. Wouldn't it be easier if I could just edit the > database property and modify the database directory? >> > > 1.06 will have expanded ALTER capabilities for all ALTER statements, > including the ALTER DATABASE statement. > Ok good. How about adding an "if exists" for: drop table if exists tablex; ? I have sql scripts that depend on this and I don't have an SQL-only workaround. Dave |
Sat, Sep 22 2007 1:13 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Dave,
<< Ok good. How about adding an "if exists" for: drop table if exists tablex; ? I have sql scripts that depend on this and I don't have an SQL-only workaround. >> You'll have to see how the new scripts in 1.06 work. With conditional IF processing, you really don't need an IF EXISTS clause anymore. -- Tim Young Elevate Software www.elevatesoft.com |
Sat, Sep 22 2007 11:19 PM | Permanent Link |
Dave Harrison | Tim Young [Elevate Software] wrote:
> Dave, > > << Ok good. How about adding an "if exists" for: > > drop table if exists tablex; > ? > > I have sql scripts that depend on this and I don't have an SQL-only > workaround. >> > > You'll have to see how the new scripts in 1.06 work. With conditional IF > processing, you really don't need an IF EXISTS clause anymore. > Ok, great. Dave |
This web page was last updated on Thursday, March 28, 2024 at 06:05 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |