CydandClaude Fable 5
63312e07f9
- BORLAND/: Borland C++ 4.52 (chosen over 4.5 by byte-match: CODE/RP/CW32.LIB
is identical to 4.52's install lib). BCC32/TLINK32/TLIB/MAKE run natively on
Win11; CODE/BT/OPT.MAK is the shipped BTL4OPT.EXE's exact flag recipe
(extender = Borland PowerPack DPMI32, not Phar Lap TNT).
- restoration/source410/: the literal 1995-form reconstruction of the missing
BT game source (never mixed into CODE/). Round 1-3 state:
* 6 of 10 surviving original TUs COMPILE CLEAN under the period toolchain
(BTMSSN, BTCNSL, BTSCNRL, BTTEAM, BTL4MODE, BTL4ARND) - first builds
since 1996.
* BT_L4/BTL4APP.CPP pilot reconstruction: 12/12 functions, Fail() lands on
its binary-recorded line 400 exactly.
* BT/BTCNSL.HPP: console wire IDs recovered from the binary's ctors
(Killed=9, Damaged=10, ScoreUpdate=13, DeathWithoutHonor=15 [T1];
TeamScore=12 flagged [T4]).
* MUNGA/: 8 engine-header backfills back-dated from the BT412 WinTesla tree
(VDATA numbering decomp-verified; AUDREND's OpenAL-era virtual removed -
the period compiler is the drift detector).
* Tooling: backdate.py (WinTesla->1995 header transform), compile410.sh
(per-TU verification sweep under authentic OPT.MAK flags).
* README: corrected roadmap - MECH.HPP is the capstone grown with the mech
TU reconstructions; BTREG.CPP green = the header-family milestone.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
47 lines
2.3 KiB
Plaintext
47 lines
2.3 KiB
Plaintext
QUERY.TXT for Borland Database Engine
|
|
"QUERY" SQL/QBE example
|
|
Copyright (c) 1994, Borland International
|
|
|
|
=====================================================================
|
|
|
|
The QUERY BDE sample application illustrates the power and flexibility
|
|
of the BDE DbiQExec() function. It also provides a convenient way to
|
|
test and run SQL or QBE queries. Working queries can be stored to
|
|
disk and retrieved for later use.
|
|
|
|
Another IDAPI feature that the QUERY example highlights is its ability
|
|
to do cross-database joins. To see how this works, make sure that you
|
|
have a server database connection established. Set up an alias to a
|
|
server using IDAPICFG. Then in the Connection dialog box within
|
|
QUERY, select that alias, enter your password, and press "Connect".
|
|
If you are successful, you'll see "Connection Is Available"; if not,
|
|
you'll see an error message which will help you troubleshoot your
|
|
connection.
|
|
|
|
Once you've established a server connection in addition to the default
|
|
connection, make sure the "<Default>" connection appears in the
|
|
"Selected Connection" frame in the Connection dialog box and press OK.
|
|
Using the default connection, a handle to a standard database, means
|
|
that local SQL will be used, and local SQL is needed to do
|
|
cross-database joins (this only applies to queries using the SQL
|
|
language).
|
|
|
|
Once this is done, you can do a cross-database join by explicitly
|
|
specifying the remote database alias as part of the tablename for the
|
|
remote tables. The syntax is similar to the syntax used to specify
|
|
aliases within Paradox for Windows (i.e. ":ALIASNAME:TABLENAME").
|
|
For example, let's say you have a local CUSTOMERS table (Paradox or
|
|
dBASE file) and an alias, "MYSERVER", to a server database on which
|
|
there is a table called CITIES. The following cross-database join
|
|
extracts all the records where the cities match.
|
|
|
|
"select *
|
|
from customer c, :MYSERVER:CITIES s
|
|
where c.City = s.CITY"
|
|
|
|
Conversely, if you don't want to use local SQL but want an SQL query
|
|
statement passed directly on to the server, make sure that the alias,
|
|
"MyServer" is specified as the Selected Connection inside the
|
|
Connection dialog box and press OK. Then instead of the syntax
|
|
"Select * from :MYSEVER:cities" you can use "Select * from cities".
|