sqlobject-discuss

[SQLObject] how to handle boolean and other types provided by DBMS?

[Bud P. B. <bu...@si...>]

Oops, another question--am I pushing my luck too far?

How do I best represent booleans with SQLObject?  PostgreSQL has a
boolean type (see
http://www.postgresql.org/docs/view.php?version=7.3&idoc=1&file=datatype-boolean.html)...

And there are many other highly interesting types such as geometric
types that I likely use in my current app.  [Yes, I marry PostgreSQL
for this app--no need to ease migration to other dbms].  

Maybe, it would be possible to add yet another subclass to Col that
has an "sqlType" keyword attribute and simply passes on what is
written there to the DBMS.  This would allow to take advantage of
"advanced" types that some DBMS provide.

Well, I'll better try to stop for today before you drop me off the
list...

--b


/-----------------------------------------------------------------
| Bud P. Bruegger, Ph.D. 
| Sistema (www.sistema.it)
| Via U. Bassi, 54
| 58100 Grosseto, Italy
| +39-0564-411682 (voice and fax)
\-----------------------------------------------------------------

Re: [SQLObject] how to handle boolean and other types provided by DBMS?

[Ian B. <ia...@co...>]

On Thu, 2003-04-10 at 12:14, Bud P.Bruegger wrote:
> Maybe, it would be possible to add yet another subclass to Col that
> has an "sqlType" keyword attribute and simply passes on what is
> written there to the DBMS.  This would allow to take advantage of
> "advanced" types that some DBMS provide.

If your class has a sqlRepr() method, then that will be called to get
the SQL representation.  I should name that __sql_repr__ or something,
though...

Anyway, that's the hook you want.

  Ian

Re: [SQLObject] how to handle boolean and other types provided by DBMS?

[Bud P. B. <bu...@si...>]

On 10 Apr 2003 13:26:27 -0500
Ian Bicking <ia...@co...> wrote:

> On Thu, 2003-04-10 at 12:14, Bud P.Bruegger wrote:
> > Maybe, it would be possible to add yet another subclass to Col that
> > has an "sqlType" keyword attribute and simply passes on what is
> > written there to the DBMS.  This would allow to take advantage of
> > "advanced" types that some DBMS provide.
> 
> If your class has a sqlRepr() method, then that will be called to get
> the SQL representation.  I should name that __sql_repr__ or something,
> though...
> 
> Anyway, that's the hook you want.
> 
>   Ian

great!  I'll have to look into this more closely...

thanks

--b