Omnis Postgres No nulls puzzle

Mike Rowan michael.rowan3 at gmail.com
Mon Jun 13 02:51:11 UTC 2022


Hi Dan

Well, I never know that. And yes, it is. Thanks for very useful input.

On Mon, Jun 13, 2022 at 11:31 AM <dlr at futurechalk.com> wrote:

> Hello Mike,
>
> The DEFAULT command is a bit misleading. It does provide a default value
> but if you have specified the column name in your sql it will not default
> to your specified value. It only works if the column is not supplied in the
> sql statement.
>
> A very annoying feature of a number of databases.
>
> Dan Ridinger
> Managing Director
>
>
>
>
> FutureChalk Software Inc.
> 20521 92A Avenue
> Langley, BC  V1M 1B7
>
> Phone No: 604.723.6837
> EMail: dlr at futurechalk.com
> www: www.futurechalk.com
>
> > On Jun 12, 2022, at 3:43 PM, Mike Rowan <michael.rowan3 at gmail.com>
> wrote:
> >
> > Morning all,
> > An example of a column definition in one of my tables in PG 14 .
> >
> > prename text COLLATE pg_catalog."default" NOT NULL DEFAULT ''::text,
> > (thats two single quotes after DEFAULT)
> >
> > I am no expert with PostgreSQL but this says to me :
> > "When this table is inserted or updated, check that this column is NOT
> NULL
> > and, if it is, set it to EMPTY."
> > Such inserts or updates are rejected due to null value in that column
> >
> > Can someone on this friendly Omnis list please tell me how I am wrong?
> > Thanks as always.
> > _____________________________________________________________
> > Manage your list subscriptions at https://lists.omnis-dev.com
> > Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>
> _____________________________________________________________
> Manage your list subscriptions at https://lists.omnis-dev.com
> Start a new message -> mailto:omnisdev-en at lists.omnis-dev.com
>


More information about the omnisdev-en mailing list