Database Documentation?

klodoma

New Member
Hi,

Where can I find a doc with the complete syntax for database structures. I looked in every Database Admin pdf from psdn.com but couldn't find any references.

I'm looking for specs for commands like:

create table
add field
create sequence
create index
drop ... etc.

Thanks in advance.
 
You'll want to look in the SQL manuals for that kind of stuff.

4GL oriented people don't deal with that kind of cruft. We just use the data dictionary to create a .df file and work with that.
 
I looked in a lot of manuals but I didn't find the sintax for thing like:

ADD INDEX "Kunden-Num" ON "KunBonusKartenUmsatz"
AREA "Indexarea"
PRIMARY
DESCRIPTION "Index nach Kunden-Num"
INDEX-FIELD "Kunden-Num" ASCENDING

ADD INDEX "Auftrag" ON "KunBonusKartenUmsatz"
AREA "Indexarea"
INDEX-FIELD "Firmen-Num" ASCENDING
INDEX-FIELD "Auftrags-Num" ASCENDING
INDEX-FIELD "Order-Count" ASCENDING

ADD TABLE "KunLadenUmsatz"
AREA "128 Recs/Block"
DESCRIPTION "Treue Bonus Karte Laden Umsatz"
DUMP-NAME "kunladen"
TABLE-TRIGGER "CREATE" NO-OVERRIDE PROCEDURE "trgKunLadenUmsatzCreate.p" CRC "59530"

We are generating a lot of "df" files to be sure that the client DB is updated, but I always have to thech the df files.

I mean, there must be somewhere written the syntax of
ADD TABLE
ADD FIELD
...and so on.

Just where? I looked in all ABL references, database administration books but couldn't find what I need.


For example I found in some Add field something like:
SQL-WIDTH 4 ?? what does that mean? In older versions there was max-width.

Regards,
Andy.
 
sql-width is v10, max-width is v9. problem with this is that if you are trying to import a df from 10 into v9 db then it will error the df - just do a global search and replace.
 
SFAIK the .df file format is not publicly available. It changes from time to time too (as the SQL Width issue demonstrates).
 
I could be wrong. Try asking tech support. Maybe they've got something squirreled away that they will share.
 
I suspect that part of the reason no one has ever bothered to write a manual for it is because it is so easy and obvious what the usage is from just creating some examples.
 
I suspect that part of the reason no one has ever bothered to write a manual for it is because it is so easy and obvious what the usage is from just creating some examples.

You could say that about just about most of the documented 4GL. It isn't obvious why the documentation is missing in this case. More likely it isn't information that is generally needed by Progress users, so other things took up the documentation budget.

klodoma, if it is *that* important to get this information, and you don't want to rely on dump-the-df-and-copy-the-format then notwithstanding the aforementioned issue of changes between versions, you may have to resort to analysing the dumping source code to catch all possibilities.

eg.(?) prodict/dump/_dmpdefs.p

Rather you than me.
 
Back
Top