Subject | Re: oracle-like "dual" quasi table |
---|---|
Author | csswa |
Post date | 2002-07-30T04:50:52Z |
You may also wish to add a constraint on your dummy 'return one'
table such as the following, which ensures that the table contains
only one record and that no editing is possible beyond initializing
the table by inserting one record.
ADD CONSTRAINT C_RONE_PK_ONE_RECORD
/* NOTE: THIS CONSTRAINT LIMITS TABLE TO ONE ENTRY AND NO EDITING */
CHECK
(
(SELECT COUNT(*) FROM T_RETURNONE) = 0
)^
Regards,
Andrew Ferguson
-- Full of unintended consequences.
table such as the following, which ensures that the table contains
only one record and that no editing is possible beyond initializing
the table by inserting one record.
ADD CONSTRAINT C_RONE_PK_ONE_RECORD
/* NOTE: THIS CONSTRAINT LIMITS TABLE TO ONE ENTRY AND NO EDITING */
CHECK
(
(SELECT COUNT(*) FROM T_RETURNONE) = 0
)^
Regards,
Andrew Ferguson
-- Full of unintended consequences.
--- In ib-support@y..., "Martijn Tonies" <m.tonies@u...> wrote:
> Hi,
>
> Most people use RDB$DATABASE - but you can also create a
> table DUAL yourself.
>
> CREATE TABLE DUAL (DUMMY(CHAR(1));
>
> COMMIT;
>
> INSERT INTO DUAL VALUES ('X');
>
> COMMIT;
>
>
> > I'd like to know if there is something like oracle's "dual" quasi-
table in
> > interbase/firebird?
> > Thank you very much for any response.
>
> Martijn Tonies
> InterBase Workbench - the developer tool for InterBase and Firebird
> http://www.interbaseworkbench.com
>
> Upscene Productions
> http://www.upscene.com
>
> "This is an object-oriented system.
> If we change anything, the users object."