and
it is most emphatically not the same as an empty string.
It is not wise to mess with the fundamental mathematics of SQL. Get used to
the fact that NULL is not empty string; embrace the fact and learn to love it.
-- Lew
---(end of broadcast)---
dex.html>
So I guess if portability of the full semantics is an issue, be careful.
-- Lew
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ys seem to me to re-invent the network database model, which lost out to
the relational model decades ago.
-- Lew
---(end of broadcast)---
TIP 5: don't forget to increase your free space map settings
Bigjim wrote:
Hi there,
I am trying to combine 2 text variable togther to form the name of a
VIEW. example
SELECT * FROM ( 'april'||'may') ;
The table (or view) part is not a character string but an identifier.
--
Lew
ution I've encountered so far to this type of problem is to have a
table of "days" with columns like isWeekday, isHoliday, julianDay,
otherTidbit, ...
Then you select or join the days within the interval of interest and factor
out weekdays, or holidays, o
of information.
Just use the syntax that best expresses your structure: PRIMARY KEY and
FOREIGN KEY.
--
Lew
---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster
ns (a multicolumn index, if appropriate), and is
the mechanism that enforces the constraint.
So they are "the same" in pg, and you don't syntactically need a NOT NULL
constraint on the column(s) involved.
--
Lew
---(end of broadcast)---
101 - 107 of 107 matches
Mail list logo