I uniqueidentifier datatype is MSSQL7's version of a GUID and for some reason the
JDBC/ODBC Bridge does not handle then well.
The next id I am getting using a function that MSSQL provides newID() which returns
the new GUID.
Brandon
>>> Fredrik Borgh <[EMAIL PROTECTED]> 05/25/00 01:24PM >>>
Sure, I've used them. They are just normal INTs or REALs depending on how
you declared them when you created the table. I'b be interested however
with how you get the next id, if you don't mind sharing
Fredrik...
On Thu, 25 May 2000, Brandon Campbell wrote:
> Fredrik,
>
> I have worked around the storage of the uniqueidentifier because I make get the next
>uniqueidentifer and then create the bean using CMP,
> but the exception below is thrown after the bean is stored and the bean is trying to
>retreive the newly stored data.
>
> It apears that the JdbcOdbc bridge may not translate this datatype correctly,
>
> Is anybody out there connecting to a MSSQL7 database that uses these
>uniqueidentifiers?
>
> If so how are you doing it?
>
> thanks in advance
>
> Brandon
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
