sqlobject-discuss

[SQLObject] TextCol

[Luke O. <lu...@me...>]

For those who like things more explicit, I was asked to create a
forced TextCol (instead of letting StringCol handle both cases).
Result:

class TextCol(StringCol):
    def __init__(self, *arg, **kw)
        #throw away possible keywords
        popKey(kw, 'length')
        popKey(kw, 'varchar')
        StringCol.__init__(self, *args, **kw)

Obviously it makes my life easier if it's checked in, but it's not too
important.

- Luke

--
 Many people are hamstrung by things like affection for
 fellow employees, honesty, desire to appear to be a
 "nice person," and other crippling limitations not
 suffered by the truly powerful and successful.

Re: [SQLObject] TextCol

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

On Fri, 2003-04-18 at 15:58, Luke Opperman wrote:
> For those who like things more explicit, I was asked to create a
> forced TextCol (instead of letting StringCol handle both cases).

I can't decide... use SQL terminology (like TEXT), or Python terminology
(like string)... for instance: notNull, notNone, or required?  One
string column with multiple SQL implementations (CHAR, VARCHAR, and
TEXT)?  And Python's strings can also be BLOBs... and XMLRPC needs
Binary types to distinguish... and someday Python is supposed to
distinguish between text and binary data...

Re: [SQLObject] TextCol

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

On 18 Apr 2003 20:09:19 -0500
Ian Bicking <ia...@co...> wrote:

> On Fri, 2003-04-18 at 15:58, Luke Opperman wrote:
> > For those who like things more explicit, I was asked to create a
> > forced TextCol (instead of letting StringCol handle both cases).
> 
> I can't decide... use SQL terminology (like TEXT), or Python terminology
> (like string)... for instance: notNull, notNone, or required?  One
> string column with multiple SQL implementations (CHAR, VARCHAR, and
> TEXT)?  And Python's strings can also be BLOBs... and XMLRPC needs
> Binary types to distinguish... and someday Python is supposed to
> distinguish between text and binary data...

On the philosphy of naming:  After proposing notNone instead of
NotNull to avoid SQL terminology, I've changed my mind and believe it
is ok to use full SQL terminology in the _column definition.  After
all, this is to decide about a physical representation in the backend.
As Ian points out, totally automatic mappings are not always optimal.  

This leaves the question on whether non-SQL backends, such as DBM or
potentially MetaKit can live with the SQL-specific
terminology/concepts...  

--b


> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
> 


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