OK. Feeling a little lazy and not wanting to write another
before triggered procedure to do the deed for me...
Has anyone thought of gunning up the column defaults so we
can specify a calculation to perform using the standard default values
only. Ie not using some other column as a basis for the calculation...
Eg. Loading up standard defaults of date('today') and user:
Create table test(
tom integer not null not default,
dick ingresdate not null with default date_part('month', 'today'),
harry varchar(32) not null with default uppercase(user)
)
Eg. Of something that would be insane:
tom integer not null not default,
dick integer not null with default (tom / 2),
harry float4 not null with default float(dick)
It's insane because the order of calculation would be unclear,
and even if you could make it clear the thought of the dependency tree
scares the tripe out of me.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 59 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 20:55:00 |
| Calls: | 810 |
| Calls today: | 1 |
| Files: | 1,287 |
| D/L today: |
11 files (21,026K bytes) |
| Messages: | 194,568 |