>What is the most reliable way to generate unique sequential keys
without
>having to resort to a record on disk updated through readu/write?
Sounds like you want to call a UUID generator.
>The keys don't have to be contiguous but only be sortable in the order
in which they
>were generated by seve
All I can offer is that it used to work in version 9.6. I haven't touched it
since. Sounds like something to take up with IBM through your support provider.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-u2-
> [EMAIL PROTECTED] On Behalf Of Anthony W. Youngman
> Sent: Saturday, April 26, 2008 9:14 AM
> To: u2-users@listserver.u2ug.org
> Subject: Re: [U2] Guaranteed unique sequential keys
>
> In message <[EMAIL PROTECTED]>, Glen B
From: Brian Leach
> ...The key was to appoint someone who was responsible for it.
> If it is anything more than trivial, it needs someone charged
> to administer it,
Conan the Librarian
> not just left to the whims of developers!...
Which brings us to the 2nd key: Build in perks for the develop
I modified my test to also include ICHECK - curiously enough, this does
not report any errors either.
It is starting to look like OPENCHECK/WRITE and ICHECK do not consider
column data type as a CONSTRAINT - sort of defeats one of the main
benfits of SQL tables doesn't it ?
-Original Messag
Well that it the point - as I stated in my original post, I have written
a test program that demonstrates that data type constraint checks are
not being performed even though the OPENCHECK statement is being used.
Hence the concern.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL
Yes I know about the OPENCHECK config setting which was why I was
intentionally using the OPENCHECK statement.
What you are saying seems to agree with how I thought things should
work, however, even when using OPENCHECK, I am able to write complete
garbage to an SQL table column defined as a DATE
Not unless you've written a ten line test program to prove that.
On Apr 27, 2008, at 10:50 PM, u2ug wrote:
Can we safely assume that any file writes on sql tables are not
subject
to data type checks or will this pop up to bite us at some point ?
---
u2-users mailing list
u2-users@listse
OPENCHK is also a parameter in uvconfig. It allows you to configure the system
to bypass integrity checks when the file is opened with OPEN - but not when the
file is opened with OPENCHK. Thus your understanding is conditionally correct,
depending on the setting of OPENCHK in uvconfig. This i
Not unless you've written a ten line test program to prove that.
On Apr 27, 2008, at 10:50 PM, u2ug wrote:
Can we safely assume that any file writes on sql tables are not
subject
to data type checks or will this pop up to bite us at some point ?
---
u2-users mailing list
u2-users@listse
10 matches
Mail list logo
