Re: [SQLObject] *id* column mandatory? BLOBS ?

[Jim V. <Jim...@no...>]

Thanks for the confirmation.

I asked this question, because we have some existing tables that do not have an
integer primary key, but I seem to be able to use SQLObject to read from them if I
tell SQLObject that some non-integer column is the *id* column (via _idName).

From your response, however, this is probably not safe.

Frank Barknecht wrote:

> Hallo,
> Jim Vickroy hat gesagt: // Jim Vickroy wrote:
>
> > May SQLObject be used with a table that has no primary key column (e.g., with a
> > table whose key is a combination of columns -- some perhaps being non-integer)?
>
> Currently no. An integer ID column is mandatory. From the docs: "You
> can override the name, but some integer primary key must exist."
>
> ciao
> --
>  Frank Barknecht                               _ ______footils.org__
>
> -------------------------------------------------------
> This SF.Net email sponsored by: Free pre-built ASP.NET sites including
> Data Reports, E-commerce, Portals, and Forums are available now.
> Download today and enter to win an XBOX or Visual Studio .NET.
> http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss