| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | SQL related... |
Carol,
> Definately 1 tables needed to handle it at minimum. Pkey will be
> the issue to make it easier so you'd add to a full nodenumber
> (4d likely bet).
That I'll be using... (zone:net/node.point, though I'm not really using the
point field for anything yet...)
> Add a possible populated 5d {at}netname to the initial set and you
> have a generatable key set with the + that covers more than fidonet.
That's being put in to the nodelist table, but I'm not certain how I'll use
it for the DNS table(s)...
> substrib(15,4) sounds right to hndle the INA
Not yet certain how I'll be doing that, but more likely to use Perl rather
than SQL, because I'd likely be needing to process more than just the one
flag... (get the set of flags, process them as an array or hash...)
> but you'd need to NVL or coalesce for null values?
Not sure about that, but there shouldn't be any null values in the table;
all fields are defined as 'NOT NULL" and have a default set...
Jame
--- BBBS/LiI v4.01 Flag
* Origin: Rocasa BBS (1:120/546)SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 120/546 544 140/1 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.