sqlobject-cvs — CVS notification

[SQL-CVS] [ sqlobject-Bugs-1501178 ] integer and float values of 0 get converted to None

[SourceForge.net <no...@so...>]

Bugs item #1501178, was opened at 2006-06-05 23:09
Message generated for change (Settings changed) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1501178&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: SQLObject from repository
>Status: Closed
>Resolution: Works For Me
Priority: 5
Submitted By: Chris Leonello (cleonello)
>Assigned to: Oleg Broytmann (phd)
Summary: integer and float values of 0 get converted to None

Initial Comment:
There is a problem with the validation/conversion of
integer and float columns.  When creating objects with
IntCol and FloatCols, values of 0 are converted to
None. String values are converted properly, however.

An example:

class test(SQLObject):
    fcol=FloatCol()
    icol=IntCol()

t = test(fcol=3.2, icol=1)
print t

<test 10L fcol=3.2000000000000002 icol=1>

t = test(fcol=0.0, icol=0)
print t

<test 11L fcol=None icol=None>

t = test(fcol='0.0', icol='0')
print t

<test 14L fcol=0.0 icol=0>

I am using SQLObject rev 1675, python2.4, formencode
0.5.1, postgresql 8.1.



----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 16:59

Message:
Logged In: YES 
user_id=4799

You examples produce the followin results for me:

SQLite:
<test 1 fcol=3.2000000000000002 icol=1>
<test 2 fcol=0.0 icol=0> # No problem here, right?

Traceback (most recent call last):
  File "./test1.py", line 23, in ?
    t = test(fcol='0.0', icol='0')
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/declarative.py",
line 92, in _wrapper
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1197, in __init__
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1221, in _create
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1080, in set
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/col.py",
line 671, in from_python
formencode.api.Invalid: expected a float in the FloatCol
'fcol', got <type 'str'> '0.0' instead

Postgres 7.4:
<test 1L fcol=3.2000000000000002 icol=1>
<test 2L fcol=0.0 icol=0> # Ok?

Traceback (most recent call last):
  File "./test1.py", line 23, in ?
    t = test(fcol='0.0', icol='0')
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/declarative.py",
line 92, in _wrapper
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1197, in __init__
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1221, in _create
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/main.py",
line 1080, in set
  File
"./SQLObject-0.7.1dev_r1684-py2.4.egg/sqlobject/col.py",
line 671, in from_python
formencode.api.Invalid: expected a float in the FloatCol
'fcol', got <type 'str'> '0.0' instead


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1501178&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496321 ] Regression in DateTimeValidator

[SourceForge.net <no...@so...>]

Bugs item #1496321, was opened at 2006-05-28 13:44
Message generated for change (Comment added) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Gritsch (markus_gritsch)
Assigned to: Oleg Broytmann (phd)
Summary: Regression in DateTimeValidator

Initial Comment:
The following change in the class DateTimeValidator
leads to different return values:

SQLObject-0.7.0:
  secs = time.mktime(stime)
  return datetime.datetime.fromtimestamp(secs)

SQLObject-0.7.1b1:
  return datetime.datetime(*stime[:7])

I think only the first 6 items of stime should be used
instead of also including the microseconds. When I
change the line to
  return datetime.datetime(*stime[:6])
everything works fine again.

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 16:53

Message:
Logged In: YES 
user_id=4799

Can you write a short test script that demonstrates the problem?

----------------------------------------------------------------------

Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 16:49

Message:
Logged In: YES 
user_id=4799

Can you write a short test script that demonstrates the problem?

----------------------------------------------------------------------

Comment By: Markus Gritsch (markus_gritsch)
Date: 2006-06-04 20:56

Message:
Logged In: YES 
user_id=553904

Additional note: The 7th value is not the micro-seconds, but
the day-of-the-week.  So the line should be definitely
changed to the one I suggested.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496321 ] Regression in DateTimeValidator

[SourceForge.net <no...@so...>]

Bugs item #1496321, was opened at 2006-05-28 13:44
Message generated for change (Settings changed) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Gritsch (markus_gritsch)
>Assigned to: Oleg Broytmann (phd)
Summary: Regression in DateTimeValidator

Initial Comment:
The following change in the class DateTimeValidator
leads to different return values:

SQLObject-0.7.0:
  secs = time.mktime(stime)
  return datetime.datetime.fromtimestamp(secs)

SQLObject-0.7.1b1:
  return datetime.datetime(*stime[:7])

I think only the first 6 items of stime should be used
instead of also including the microseconds. When I
change the line to
  return datetime.datetime(*stime[:6])
everything works fine again.

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 16:49

Message:
Logged In: YES 
user_id=4799

Can you write a short test script that demonstrates the problem?

----------------------------------------------------------------------

Comment By: Markus Gritsch (markus_gritsch)
Date: 2006-06-04 20:56

Message:
Logged In: YES 
user_id=553904

Additional note: The 7th value is not the micro-seconds, but
the day-of-the-week.  So the line should be definitely
changed to the one I suggested.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1494674 ] attribute names ignored on join columns.

[SourceForge.net <no...@so...>]

Bugs item #1494674, was opened at 2006-05-25 04:56
Message generated for change (Settings changed) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Simon Wittber (simonwittber)
>Assigned to: Oleg Broytmann (phd)
Summary: attribute names ignored on join columns.

Initial Comment:
This is using python2.4-sqlobject_0.6-1ubuntu2_all.deb


in a module called dbo.py:

__connection__ =
connectionForURI("postgres://xxx:xxx@127.0.0.1/xxx")

class Worker(SQLObject):
    name = StringCol(length=128, alternateID=True)
    time_entries = MultipleJoin('TimeEntry')
    timesheets = MultipleJoin('Timesheet')
    aliases = MultipleJoin('Alias')
    department = ForeignKey('Department')


>>> import dbo
>>> w = dbo.Worker.get(1)
>>> [i for i in dir(w) if "time" in str(i)]
['_SO_get_timeEntrys', '_SO_get_timesheets',
'_get_timeEntrys', '_get_timesheets', 'timeEntrys',
'timesheets']
>>>


Notice that my time_entries attribute in the Worker
class has been ignored, and replaced with a
'timeEntrys' attribute.

----------------------------------------------------------------------

Comment By: Simon Wittber (simonwittber)
Date: 2006-05-25 05:00

Message:
Logged In: YES 
user_id=598842

I've just checked out SVN trunk, and this problem has been
fixed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

[SQL-CVS] [ sqlobject-Patches-1496016 ] Encode queries to unicode for MySQLdb 1.2.1

[SourceForge.net <no...@so...>]

Patches item #1496016, was opened at 2006-05-27 18:49
Message generated for change (Comment added) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1496016&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Neil Muller (nitwit)
Assigned to: Nobody/Anonymous (nobody)
Summary: Encode queries  to unicode for MySQLdb 1.2.1

Initial Comment:
MySQLdb 1.2.1 assumes that queries will be unicode
objects rather than string objects. The attached patch
aims to do the right thing. The assumption about alwasy
encoding using the charset specified in the mysql URI
is somewhat questionable, and it may be better to try
and infer self.encoding from the locale instead.

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 16:37

Message:
Logged In: YES 
user_id=4799

Your patch starts with "if MySQLdb.version_info[0]>0...". 
You probably want "if MySQLdb.version_info[0]>1..."?

Your patch adds "use_unicode"... which is already there. ;)

BTW, in case of MySQLbd 1.2.1+ where self.need_unicode=True
you probbaly wants to always set use_unicode to 1, no? What
if the user sets use_unicode=False? Would MySQLdb revert to
ascii queries and responces?

Infering self.encoding from the environment is the
application's task, I think. Let's the user decide what
encoding (s)he wants.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1496016&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496321 ] Regression in DateTimeValidator

[SourceForge.net <no...@so...>]

Bugs item #1496321, was opened at 2006-05-28 11:44
Message generated for change (Comment added) made by markus_gritsch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Gritsch (markus_gritsch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Regression in DateTimeValidator

Initial Comment:
The following change in the class DateTimeValidator
leads to different return values:

SQLObject-0.7.0:
  secs = time.mktime(stime)
  return datetime.datetime.fromtimestamp(secs)

SQLObject-0.7.1b1:
  return datetime.datetime(*stime[:7])

I think only the first 6 items of stime should be used
instead of also including the microseconds. When I
change the line to
  return datetime.datetime(*stime[:6])
everything works fine again.

----------------------------------------------------------------------

>Comment By: Markus Gritsch (markus_gritsch)
Date: 2006-06-04 18:56

Message:
Logged In: YES 
user_id=553904

Additional note: The 7th value is not the micro-seconds, but
the day-of-the-week.  So the line should be definitely
changed to the one I suggested.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1501178 ] integer and float values of 0 get converted to None

[SourceForge.net <no...@so...>]

Bugs item #1501178, was opened at 2006-06-05 15:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1501178&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: SQLObject from repository
Status: Open
Resolution: None
Priority: 5
Submitted By: Chris Leonello (cleonello)
Assigned to: Nobody/Anonymous (nobody)
Summary: integer and float values of 0 get converted to None

Initial Comment:
There is a problem with the validation/conversion of
integer and float columns.  When creating objects with
IntCol and FloatCols, values of 0 are converted to
None. String values are converted properly, however.

An example:

class test(SQLObject):
    fcol=FloatCol()
    icol=IntCol()

t = test(fcol=3.2, icol=1)
print t

<test 10L fcol=3.2000000000000002 icol=1>

t = test(fcol=0.0, icol=0)
print t

<test 11L fcol=None icol=None>

t = test(fcol='0.0', icol='0')
print t

<test 14L fcol=0.0 icol=0>

I am using SQLObject rev 1675, python2.4, formencode
0.5.1, postgresql 8.1.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1501178&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496014 ] None in enumValues fails

[SourceForge.net <no...@so...>]

Bugs item #1496014, was opened at 2006-05-27 16:42
Message generated for change (Comment added) made by nitwit
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496014&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MySQL
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Neil Muller (nitwit)
Assigned to: Nobody/Anonymous (nobody)
Summary: None in enumValues fails

Initial Comment:
SQLObject-0.7.1b1

MySQL does not allow NULL inside the ENUM statemnt, so
the construction
EnumCol(enumValues=['a','b',None],default=None) will fail.

Since this construction works fine with sqlite and
postgresql, this is an issue. The attached patch fixes
the problem here.



----------------------------------------------------------------------

>Comment By: Neil Muller (nitwit)
Date: 2006-05-29 22:39

Message:
Logged In: YES 
user_id=698097

I was pointed at
http://archives.postgresql.org/pgsql-sql/2004-12/msg00065.php,
which illustrates that NULL in the check constraint approach
used to implement EnumCol for postges and other databases
behave in an unexpected way due to the three state logic SQL
uses. Thus a believe this second patch, which excludes Nones
from all the database backends should be prefferred.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496014&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496321 ] Regression in DateTimeValidator

[SourceForge.net <no...@so...>]

Bugs item #1496321, was opened at 2006-05-28 11:44
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Markus Gritsch (markus_gritsch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Regression in DateTimeValidator

Initial Comment:
The following change in the class DateTimeValidator
leads to different return values:

SQLObject-0.7.0:
  secs = time.mktime(stime)
  return datetime.datetime.fromtimestamp(secs)

SQLObject-0.7.1b1:
  return datetime.datetime(*stime[:7])

I think only the first 6 items of stime should be used
instead of also including the microseconds. When I
change the line to
  return datetime.datetime(*stime[:6])
everything works fine again.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496321&group_id=74338

[SQL-CVS] [ sqlobject-Patches-1496016 ] Encode queries to unicode for MySQLdb 1.2.1

[SourceForge.net <no...@so...>]

Patches item #1496016, was opened at 2006-05-27 16:49
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1496016&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Neil Muller (nitwit)
Assigned to: Nobody/Anonymous (nobody)
Summary: Encode queries  to unicode for MySQLdb 1.2.1

Initial Comment:
MySQLdb 1.2.1 assumes that queries will be unicode
objects rather than string objects. The attached patch
aims to do the right thing. The assumption about alwasy
encoding using the charset specified in the mysql URI
is somewhat questionable, and it may be better to try
and infer self.encoding from the locale instead.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1496016&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1496014 ] None in enumValues fails

[SourceForge.net <no...@so...>]

Bugs item #1496014, was opened at 2006-05-27 16:42
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496014&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: MySQL
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Neil Muller (nitwit)
Assigned to: Nobody/Anonymous (nobody)
Summary: None in enumValues fails

Initial Comment:
SQLObject-0.7.1b1

MySQL does not allow NULL inside the ENUM statemnt, so
the construction
EnumCol(enumValues=['a','b',None],default=None) will fail.

Since this construction works fine with sqlite and
postgresql, this is an issue. The attached patch fixes
the problem here.



----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1496014&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1495030 ] sql drop fails with soClasses

[SourceForge.net <no...@so...>]

Bugs item #1495030, was opened at 2006-05-25 08:48
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1495030&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: sql drop fails with soClasses

Initial Comment:

sqlobject-admin sql create

respects soClasses, but sqlobject-admin drop tries to 
drop the tables in the same order instead of in the
reverse order. 

See

http://trac.turbogears.org/turbogears/ticket/882

for an example and possible patch.

Arthur Clune (pu...@cl...)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1495030&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1494674 ] attribute names ignored on join columns.

[SourceForge.net <no...@so...>]

Bugs item #1494674, was opened at 2006-05-25 08:56
Message generated for change (Comment added) made by simonwittber
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Simon Wittber (simonwittber)
Assigned to: Nobody/Anonymous (nobody)
Summary: attribute names ignored on join columns.

Initial Comment:
This is using python2.4-sqlobject_0.6-1ubuntu2_all.deb


in a module called dbo.py:

__connection__ =
connectionForURI("postgres://xxx:xxx@127.0.0.1/xxx")

class Worker(SQLObject):
    name = StringCol(length=128, alternateID=True)
    time_entries = MultipleJoin('TimeEntry')
    timesheets = MultipleJoin('Timesheet')
    aliases = MultipleJoin('Alias')
    department = ForeignKey('Department')


>>> import dbo
>>> w = dbo.Worker.get(1)
>>> [i for i in dir(w) if "time" in str(i)]
['_SO_get_timeEntrys', '_SO_get_timesheets',
'_get_timeEntrys', '_get_timesheets', 'timeEntrys',
'timesheets']
>>>


Notice that my time_entries attribute in the Worker
class has been ignored, and replaced with a
'timeEntrys' attribute.

----------------------------------------------------------------------

>Comment By: Simon Wittber (simonwittber)
Date: 2006-05-25 09:00

Message:
Logged In: YES 
user_id=598842

I've just checked out SVN trunk, and this problem has been
fixed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1494674 ] attribute names ignored on join columns.

[SourceForge.net <no...@so...>]

Bugs item #1494674, was opened at 2006-05-25 08:56
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Simon Wittber (simonwittber)
Assigned to: Nobody/Anonymous (nobody)
Summary: attribute names ignored on join columns.

Initial Comment:
This is using python2.4-sqlobject_0.6-1ubuntu2_all.deb


in a module called dbo.py:

__connection__ =
connectionForURI("postgres://xxx:xxx@127.0.0.1/xxx")

class Worker(SQLObject):
    name = StringCol(length=128, alternateID=True)
    time_entries = MultipleJoin('TimeEntry')
    timesheets = MultipleJoin('Timesheet')
    aliases = MultipleJoin('Alias')
    department = ForeignKey('Department')


>>> import dbo
>>> w = dbo.Worker.get(1)
>>> [i for i in dir(w) if "time" in str(i)]
['_SO_get_timeEntrys', '_SO_get_timesheets',
'_get_timeEntrys', '_get_timesheets', 'timeEntrys',
'timesheets']
>>>


Notice that my time_entries attribute in the Worker
class has been ignored, and replaced with a
'timeEntrys' attribute.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1494674&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1432190 ] Table creation order for foreign key constraints

[SourceForge.net <no...@so...>]

Bugs item #1432190, was opened at 2006-02-15 17:22
Message generated for change (Comment added) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1432190&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Björn Lindqvist (sonderblade)
>Assigned to: Oleg Broytmann (phd)
Summary: Table creation order for foreign key constraints

Initial Comment:
Note: I had to apply my patch in
https://sourceforge.net/tracker/index.php?func=detail&aid=1432176&group_id=74338&atid=540674
otherwise the foreign key constrains would be
completely ignored. I have a simple model.py file
containing my two tables like this:

    class Network(SQLObject):
        name = StringCol(alternateID = True, length = 80)

    class Channel(SQLObject):
        network = ForeignKey("Network", notNull = True)
        name = StringCol()

Using "tg-admin sql sql" produces a listing like this:

CREATE TABLE channel (
    id INT PRIMARY KEY AUTO_INCREMENT,
    network_id INT NOT NULL,
    name TEXT
);

CREATE TABLE network (
    id INT PRIMARY KEY AUTO_INCREMENT,
    name VARCHAR(80) NOT NULL UNIQUE
);

ALTER TABLE channel ADD CONSTRAINT
channel_network_id_exists FOREIGN KEY (network_id)
REFERENCES network (id);

Creating these two tables manually work:

    Network.createTable()
    Channel.createTable()

But when I try to create them using "tg-admin sql
create" (which just wraps "sqlobject-admin create") I
get the following exception:

Traceback (most recent call last):
  File "/usr/bin/tg-admin", line 7, in ?
    sys.exit(
  File
"/usr/lib/python2.4/site-packages/TurboGears-0.9a0dev_r778-py2.4.egg/turbogears/command/base.py",
line 269, in main
    command.run()
  File
"/usr/lib/python2.4/site-packages/TurboGears-0.9a0dev_r778-py2.4.egg/turbogears/command/base.py",
line 129, in run
    command.the_runner.run(sys.argv)
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/manager/command.py",
line 100, in run
    runner.run()
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/manager/command.py",
line 231, in run
    self.command()
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/manager/command.py",
line 583, in command
    tableConstraints = soClass.createTable()
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/main.py",
line 1372, in createTable
    conn.query(constraint)
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/dbconnection.py",
line 314, in query
    return self._runWithConnection(self._query, s)
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/dbconnection.py",
line 228, in _runWithConnection
    val = meth(conn, *args)
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/dbconnection.py",
line 311, in _query
    self._executeRetry(conn, conn.cursor(), s)
  File
"/usr/lib/python2.4/site-packages/SQLObject-0.8dev_r1596-py2.4.egg/sqlobject/mysql/mysqlconnection.py",
line 66, in _executeRetry
    return cursor.execute(query)
  File
"/usr/lib/python2.4/site-packages/MySQLdb/cursors.py",
line 137, in execute
    self.errorhandler(self, exc, value)
  File
"/usr/lib/python2.4/site-packages/MySQLdb/connections.py",
line 33, in defaulterrorhandler
    raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1005, "Can't
create table './test/#sql-1cf0_b9.frm' (errno: 150)")

The problem is because sqlobject creates the Channel
table before the Network table and therefore the query
(despite the order that "tg-admin sql sql" seem to
suggest):

    ALTER TABLE channel ADD CONSTRAINT
channel_network_id_exists FOREIGN KEY (network_id)
REFERENCES network (id);

is executed before the Network table has been created.
I think the problem can be solved by making it so all
constraint statements are executed after the create
table statements are executed.  

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-05-23 17:22

Message:
Logged In: YES 
user_id=4799

The patch
https://sourceforge.net/tracker/index.php?func=detail&aid=1432176&group_id=74338&atid=540674
was applied. Does it help?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1432190&group_id=74338

[SQL-CVS] [ sqlobject-Bugs-1493586 ] destroySelf() must remove the object from related joins

[SourceForge.net <no...@so...>]

Bugs item #1493586, was opened at 2006-05-23 17:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1493586&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Oleg Broytmann (phd)
Assigned to: Nobody/Anonymous (nobody)
Summary: destroySelf() must remove the object from related joins

Initial Comment:
.destroySelf() must remove the object being destroyed
from all related joins. Something like this:

class Service(Base):
    groups = RelatedJoin("ServiceGroup")

    def destroySelf(self):
        for group in self.groups:
            self.removeServiceGroup(group)
        super(Service, self).destroySelf()

class ServiceGroup(Base):
    services = RelatedJoin("Service")

    def destroySelf(self):
        for service in self.services:
            self.removeService(service)
        super(ServiceGroup, self).destroySelf()

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1493586&group_id=74338

[SQL-CVS] [ sqlobject-Patches-1491098 ] test for relative paths for connections

[SourceForge.net <no...@so...>]

Patches item #1491098, was opened at 2006-05-18 21:05
Message generated for change (Comment added) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1491098&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: test for relative paths for connections

Initial Comment:
I can't add this to the previous patch/bug so I'm
adding it as a new item. I have got a sf account but it
won't let me log in.

Cheers,

~andy
-- 
Andy Kilner <an...@an...>

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-05-23 17:13

Message:
Logged In: YES 
user_id=4799

We've decided not to allow relative URIs.

----------------------------------------------------------------------

Comment By: Oleg Broytmann (phd)
Date: 2006-05-18 21:33

Message:
Logged In: YES 
user_id=4799

You have forgotten to attach the patch. Probably just forgot
to check the checkbox. Please resubmit.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1491098&group_id=74338

[SQL-CVS] [ sqlobject-Patches-1489030 ] Fix relative paths for connections

[SourceForge.net <no...@so...>]

Patches item #1489030, was opened at 2006-05-15 22:13
Message generated for change (Comment added) made by phd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1489030&group_id=74338

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Wont Fix
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Fix relative paths for connections

Initial Comment:
When creating a DBConnection such as sqlite:/members.db
an extra / is added to the beginning of the path. This
patch moves that to the individual if statements
depending on whether it is a relative, absolute or
other type of path.

It's a simple fix, probably could be tidied up to not
repeat itself but this works and it makes sqlite happy.

Cheers,

~andy
-- 
Andy Kilner <an...@an...>

----------------------------------------------------------------------

>Comment By: Oleg Broytmann (phd)
Date: 2006-05-23 17:12

Message:
Logged In: YES 
user_id=4799

We've decided not to allow relative URIs.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1489030&group_id=74338

[SQL-CVS] r1793 - in home/phd/SQLObject/paramstyles/sqlobject: firebird maxdb sybase

[<sub...@co...>]

Author: phd
Date: 2006-05-23 06:13:58 -0600 (Tue, 23 May 2006)
New Revision: 1793

Modified:
   home/phd/SQLObject/paramstyles/sqlobject/firebird/firebirdconnection.py
   home/phd/SQLObject/paramstyles/sqlobject/maxdb/maxdbconnection.py
   home/phd/SQLObject/paramstyles/sqlobject/sybase/sybaseconnection.py
Log:
Merged patches from the revisions 1789:1792 from the trunk

Modified: home/phd/SQLObject/paramstyles/sqlobject/firebird/firebirdconnection.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/firebird/firebirdconnection.py	2006-05-23 12:11:01 UTC (rev 1792)
+++ home/phd/SQLObject/paramstyles/sqlobject/firebird/firebirdconnection.py	2006-05-23 12:13:58 UTC (rev 1793)
@@ -128,6 +128,9 @@
                    (soClass.sqlmeta.table, self.createColumns(soClass)))
         self.query("CREATE GENERATOR GEN_%s" % soClass.sqlmeta.table)
 
+    def createReferenceConstraint(self, soClass, col):
+        return None
+
     def createColumn(self, soClass, col):
         return col.firebirdCreateSQL()
 

Modified: home/phd/SQLObject/paramstyles/sqlobject/maxdb/maxdbconnection.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/maxdb/maxdbconnection.py	2006-05-23 12:11:01 UTC (rev 1792)
+++ home/phd/SQLObject/paramstyles/sqlobject/maxdb/maxdbconnection.py	2006-05-23 12:13:58 UTC (rev 1793)
@@ -26,7 +26,7 @@
 
     def __str__(self):
         return repr(self.value)
-    
+
 class LowerBoundOfSliceIsNotSupported(maxdbException):
     def __init__(self, value):
         maxdbException.__init__(self, '')
@@ -52,14 +52,14 @@
             self,
             "No primary key was defined on table %r" % value)
 
-SAPDBMAX_ID_LENGTH=32  
+SAPDBMAX_ID_LENGTH=32
 
 class MaxdbConnection(DBAPI):
-    
+
     supportTransactions = True
     dbName = 'maxdb'
     schemes = [dbName]
-   
+
     def __init__ (self, user, password, database,
                   host='', autoCommit=1, sqlmode='internal',
                   isolation=None, timeout=None, **kw):
@@ -102,7 +102,7 @@
         conn.__init__(self.user, self.password, self.database,
                       self.host,
                       **self._getConfigParams(self.sqlmode,auto))
- 
+
     def createSequenceName(self,table):
         """
         sequence name are builded with the concatenation of the table
@@ -151,16 +151,16 @@
         limit = ' ROWNO   <= %d ' % (end)
         return self.sqlAddLimit(query,limit)
 
-    
+
     def createTable(self, soClass):
         #we create the table in a transaction because the addition of the
-        #table and the sequence must be atomic 
+        #table and the sequence must be atomic
 
-        #i tried to use the transaction class but i get a recursion limit error    
+        #i tried to use the transaction class but i get a recursion limit error
         #t=self.transaction()
         # t.query('CREATE TABLE %s (\n%s\n)' % \
         #            (soClass.sqlmeta.table, self.createColumns(soClass)))
-        # 
+        #
         # t.query("CREATE SEQUENCE %s" % self.createSequenceName(soClass.sqlmeta.table))
         # t.commit()
         #so use transaction when the problem will be solved
@@ -168,7 +168,7 @@
                    (soClass.sqlmeta.table, self.createColumns(soClass)))
         self.query("CREATE SEQUENCE %s"
                    % self.createSequenceName(soClass.sqlmeta.table))
- 
+
     def createReferenceConstraint(self, soClass, col):
         return col.maxdbCreateReferenceConstraint()
 
@@ -184,7 +184,7 @@
 
     def dropTable(self, tableName,cascade=False):
         #we drop the table in a transaction because the removal of the
-        #table and the sequence must be atomic 
+        #table and the sequence must be atomic
         #i tried to use the transaction class but i get a recursion limit error
         # try:
         #     t=self.transaction()
@@ -224,7 +224,7 @@
     GET_PK_AND_FK = """
     SELECT constraint_cols.column_name, constraints.constraint_type,
            refname,reftablename
-    FROM user_cons_columns constraint_cols 
+    FROM user_cons_columns constraint_cols
     INNER JOIN user_constraints constraints
     ON constraint_cols.constraint_name = constraints.constraint_name
     LEFT OUTER JOIN show_foreign_key fk
@@ -244,7 +244,7 @@
             pkmap[col_name]=False
             if cons_type == 'R':
                 keymap[col_name]=reftable.lower()
-                
+
             elif cons_type == 'P':
                 pkmap[col_name]=True
 
@@ -255,14 +255,14 @@
              data_scale) in colData:
             # id is defined as primary key --> ok
             # We let sqlobject raise error if the 'id' is used for another column
-            field_name = field.lower() 
+            field_name = field.lower()
             if field_name == 'id' and  pkmap[field_name]:
                 continue
-            
+
             colClass, kw = self.guessClass(data_type,data_len,data_scale)
             kw['name'] = field_name
 
-            if nullAllowed == 'Y' : 
+            if nullAllowed == 'Y' :
                 nullAllowed=False
             else:
                 nullAllowed=True
@@ -275,9 +275,9 @@
                 kw['foreignKey'] = keymap[field_name]
 
             results.append(colClass(**kw))
-            
+
         return results
-    
+
     _numericTypes=['INTEGER', 'INT','SMALLINT']
     _dateTypes=['DATE','TIME','TIMESTAMP']
 

Modified: home/phd/SQLObject/paramstyles/sqlobject/sybase/sybaseconnection.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/sybase/sybaseconnection.py	2006-05-23 12:11:01 UTC (rev 1792)
+++ home/phd/SQLObject/paramstyles/sqlobject/sybase/sybaseconnection.py	2006-05-23 12:13:58 UTC (rev 1793)
@@ -98,6 +98,9 @@
         # XXX Sybase doesn't support LIMIT
         return query
 
+    def createReferenceConstraint(self, soClass, col):
+        return None
+
     def createColumn(self, soClass, col):
         return col.sybaseCreateSQL()
 

[SQL-CVS] r1792 - in SQLObject/trunk/sqlobject: firebird sybase

[<sub...@co...>]

Author: phd
Date: 2006-05-23 06:11:01 -0600 (Tue, 23 May 2006)
New Revision: 1792

Modified:
   SQLObject/trunk/sqlobject/firebird/firebirdconnection.py
   SQLObject/trunk/sqlobject/sybase/sybaseconnection.py
Log:
Added createReferenceConstraint that returns None.


Modified: SQLObject/trunk/sqlobject/firebird/firebirdconnection.py
===================================================================
--- SQLObject/trunk/sqlobject/firebird/firebirdconnection.py	2006-05-23 12:09:46 UTC (rev 1791)
+++ SQLObject/trunk/sqlobject/firebird/firebirdconnection.py	2006-05-23 12:11:01 UTC (rev 1792)
@@ -128,6 +128,9 @@
                    (soClass.sqlmeta.table, self.createColumns(soClass)))
         self.query("CREATE GENERATOR GEN_%s" % soClass.sqlmeta.table)
 
+    def createReferenceConstraint(self, soClass, col):
+        return None
+
     def createColumn(self, soClass, col):
         return col.firebirdCreateSQL()
 

Modified: SQLObject/trunk/sqlobject/sybase/sybaseconnection.py
===================================================================
--- SQLObject/trunk/sqlobject/sybase/sybaseconnection.py	2006-05-23 12:09:46 UTC (rev 1791)
+++ SQLObject/trunk/sqlobject/sybase/sybaseconnection.py	2006-05-23 12:11:01 UTC (rev 1792)
@@ -98,6 +98,9 @@
         # XXX Sybase doesn't support LIMIT
         return query
 
+    def createReferenceConstraint(self, soClass, col):
+        return None
+
     def createColumn(self, soClass, col):
         return col.sybaseCreateSQL()
 

[SQL-CVS] r1791 - SQLObject/trunk/sqlobject/maxdb

[<sub...@co...>]

Author: phd
Date: 2006-05-23 06:09:46 -0600 (Tue, 23 May 2006)
New Revision: 1791

Modified:
   SQLObject/trunk/sqlobject/maxdb/maxdbconnection.py
Log:
Removed trailing spaces.


Modified: SQLObject/trunk/sqlobject/maxdb/maxdbconnection.py
===================================================================
--- SQLObject/trunk/sqlobject/maxdb/maxdbconnection.py	2006-05-23 04:09:19 UTC (rev 1790)
+++ SQLObject/trunk/sqlobject/maxdb/maxdbconnection.py	2006-05-23 12:09:46 UTC (rev 1791)
@@ -26,7 +26,7 @@
 
     def __str__(self):
         return repr(self.value)
-    
+
 class LowerBoundOfSliceIsNotSupported(maxdbException):
     def __init__(self, value):
         maxdbException.__init__(self, '')
@@ -52,14 +52,14 @@
             self,
             "No primary key was defined on table %r" % value)
 
-SAPDBMAX_ID_LENGTH=32  
+SAPDBMAX_ID_LENGTH=32
 
 class MaxdbConnection(DBAPI):
-    
+
     supportTransactions = True
     dbName = 'maxdb'
     schemes = [dbName]
-   
+
     def __init__ (self, user, password, database,
                   host='', autoCommit=1, sqlmode='internal',
                   isolation=None, timeout=None, **kw):
@@ -102,7 +102,7 @@
         conn.__init__(self.user, self.password, self.database,
                       self.host,
                       **self._getConfigParams(self.sqlmode,auto))
- 
+
     def createSequenceName(self,table):
         """
         sequence name are builded with the concatenation of the table
@@ -151,16 +151,16 @@
         limit = ' ROWNO   <= %d ' % (end)
         return self.sqlAddLimit(query,limit)
 
-    
+
     def createTable(self, soClass):
         #we create the table in a transaction because the addition of the
-        #table and the sequence must be atomic 
+        #table and the sequence must be atomic
 
-        #i tried to use the transaction class but i get a recursion limit error    
+        #i tried to use the transaction class but i get a recursion limit error
         #t=self.transaction()
         # t.query('CREATE TABLE %s (\n%s\n)' % \
         #            (soClass.sqlmeta.table, self.createColumns(soClass)))
-        # 
+        #
         # t.query("CREATE SEQUENCE %s" % self.createSequenceName(soClass.sqlmeta.table))
         # t.commit()
         #so use transaction when the problem will be solved
@@ -168,7 +168,7 @@
                    (soClass.sqlmeta.table, self.createColumns(soClass)))
         self.query("CREATE SEQUENCE %s"
                    % self.createSequenceName(soClass.sqlmeta.table))
- 
+
     def createReferenceConstraint(self, soClass, col):
         return col.maxdbCreateReferenceConstraint()
 
@@ -184,7 +184,7 @@
 
     def dropTable(self, tableName,cascade=False):
         #we drop the table in a transaction because the removal of the
-        #table and the sequence must be atomic 
+        #table and the sequence must be atomic
         #i tried to use the transaction class but i get a recursion limit error
         # try:
         #     t=self.transaction()
@@ -224,7 +224,7 @@
     GET_PK_AND_FK = """
     SELECT constraint_cols.column_name, constraints.constraint_type,
            refname,reftablename
-    FROM user_cons_columns constraint_cols 
+    FROM user_cons_columns constraint_cols
     INNER JOIN user_constraints constraints
     ON constraint_cols.constraint_name = constraints.constraint_name
     LEFT OUTER JOIN show_foreign_key fk
@@ -244,7 +244,7 @@
             pkmap[col_name]=False
             if cons_type == 'R':
                 keymap[col_name]=reftable.lower()
-                
+
             elif cons_type == 'P':
                 pkmap[col_name]=True
 
@@ -255,14 +255,14 @@
              data_scale) in colData:
             # id is defined as primary key --> ok
             # We let sqlobject raise error if the 'id' is used for another column
-            field_name = field.lower() 
+            field_name = field.lower()
             if field_name == 'id' and  pkmap[field_name]:
                 continue
-            
+
             colClass, kw = self.guessClass(data_type,data_len,data_scale)
             kw['name'] = field_name
 
-            if nullAllowed == 'Y' : 
+            if nullAllowed == 'Y' :
                 nullAllowed=False
             else:
                 nullAllowed=True
@@ -275,9 +275,9 @@
                 kw['foreignKey'] = keymap[field_name]
 
             results.append(colClass(**kw))
-            
+
         return results
-    
+
     _numericTypes=['INTEGER', 'INT','SMALLINT']
     _dateTypes=['DATE','TIME','TIMESTAMP']
 

[SQL-CVS] r1790 - in SQLObject/tags: . 0.7.1b1

[<sub...@co...>]

Author: ianb
Date: 2006-05-22 22:09:19 -0600 (Mon, 22 May 2006)
New Revision: 1790

Added:
   SQLObject/tags/0.7.1b1/
Modified:
   SQLObject/tags/0.7.1b1/setup.cfg
   SQLObject/tags/0.7.1b1/setup.py
Log:
tag for release


Copied: SQLObject/tags/0.7.1b1 (from rev 1789, SQLObject/branches/0.7-bugfix)

Modified: SQLObject/tags/0.7.1b1/setup.cfg
===================================================================
--- SQLObject/branches/0.7-bugfix/setup.cfg	2006-05-22 12:52:40 UTC (rev 1789)
+++ SQLObject/tags/0.7.1b1/setup.cfg	2006-05-23 04:09:19 UTC (rev 1790)
@@ -1,7 +1,3 @@
-[egg_info]
-tag_build = dev
-tag_svn_revision = true
-
 [pudge]
 title = SQLObject
 dest = docs/html

Modified: SQLObject/tags/0.7.1b1/setup.py
===================================================================
--- SQLObject/branches/0.7-bugfix/setup.py	2006-05-22 12:52:40 UTC (rev 1789)
+++ SQLObject/tags/0.7.1b1/setup.py	2006-05-23 04:09:19 UTC (rev 1790)
@@ -19,7 +19,7 @@
     DistributionMetadata.download_url = None
 
 setup(name="SQLObject",
-      version="0.7.1",
+      version="0.7.1b1",
       description="Object-Relational Manager, aka database wrapper",
       long_description="""\
 SQLObject is a popular *Object Relational Manager* for providing an
@@ -51,7 +51,7 @@
       license="LGPL",
       packages=["sqlobject"] + ['sqlobject.%s' % package for package in subpackages],
       scripts=["scripts/sqlobject-admin"],
-      install_requires=["FormEncode>=0.2.2"],
+      install_requires=["FormEncode>=0.5"],
       extras_require={
         'postgresql': ['psycopg'],
         'mysql': ['MySQLdb'],

[SQL-CVS] r1789 - SQLObject/docs

[<sub...@co...>]

Author: phd
Date: 2006-05-22 06:52:40 -0600 (Mon, 22 May 2006)
New Revision: 1789

Modified:
   SQLObject/docs/News.txt
   SQLObject/docs/SQLObject.txt
Log:
Recollected features and bug fixes for 0.7.1.


Modified: SQLObject/docs/News.txt
===================================================================
--- SQLObject/docs/News.txt	2006-05-22 12:52:16 UTC (rev 1788)
+++ SQLObject/docs/News.txt	2006-05-22 12:52:40 UTC (rev 1789)
@@ -17,12 +17,6 @@
   Constraints (in the DBMSes that support constraints) are added after the
   tables have been created.
 
-* ``RelatedJoin`` and ``SQLRelatedJoin`` objects have a
-  ``createRelatedTable`` keyword argument (default ``True``).  If
-  ``False``, then the related table won't be automatically created;
-  instead you must manually create it (e.g., with explicit SQLObject
-  classes for the joins).
-
 * Added ``createSQL`` as an option for sqlmeta. Here you can add
   related SQL you want executed by sqlobject-admin create after table
   creation. createSQL expects a string, list, or dictionary. If using
@@ -51,21 +45,80 @@
   transactions.  Available as ``egg:SQLObject`` in Paste Deploy
   configuration files.
 
+* New joins! ManyToMany and OneToMany; not fully documented yet, but still more sensible and smarter.
+
+Small Features
+--------------
+
+* Configurable client character set (encoding) for MySQL.
+
+* Added a close option to .commit(), so you can close the transaction as you commit it
+
+* DecimalValidator.
+
+* Added .expireAll() methods to sqlmeta and connection objects, to expire all instances in those cases.
+
+* String IDs.
+
+* FOREIGN KEY for MySQL.
+
+Bug Fixes
+---------
+
+* Fixed problem with sqlite and threads; connections are no longer shared between threads for sqlite (except for :memory:)
+
 SQLObject 0.7.1
 ===============
 
-* Added ``TimeCol``.
+Features & Interface
+--------------------
 
 * Added support for psycopg2_
 
 .. _psycopg2: http://initd.org/projects/psycopg2
 
-* Added support for MSSQL_.
+* Added support for MSSQL.
 
-.. _MSSQL: SQLObject.html#ms-sql-server
+* Added ``TimeCol``.
 
+* ``RelatedJoin`` and ``SQLRelatedJoin`` objects have a
+  ``createRelatedTable`` keyword argument (default ``True``).  If
+  ``False``, then the related table won't be automatically created;
+  instead you must manually create it (e.g., with explicit SQLObject
+  classes for the joins).
+
 * Implemented ``RLIKE`` (reguluar expression LIKE).
 
+Small Features
+--------------
+
+* Select over RelatedJoin.
+
+* SQLite foreign keys.
+
+* Postgres DB URIs with a non-default path to unix socket.
+
+* Allow the use of foreign keys in selects.
+
+* Implemented addColumn() for SQLite.
+
+* With PySQLite2 use encode()/decode() from PySQLite1 for BLOBCol if available; else use base64.
+
+Bug Fixes
+---------
+
+* Cull patch (clear cache).
+
+* .destroySelf() inside a transaction.
+
+* Synchronize main connection cache during transaction commit.
+
+* Ordering joins with NULLs.
+
+* Fixed bugs with plain/non-plain setters.
+
+* Lots of other bug fixes.
+
 SQLObject 0.7.0
 ===============
 

Modified: SQLObject/docs/SQLObject.txt
===================================================================
--- SQLObject/docs/SQLObject.txt	2006-05-22 12:52:16 UTC (rev 1788)
+++ SQLObject/docs/SQLObject.txt	2006-05-22 12:52:40 UTC (rev 1789)
@@ -58,9 +58,9 @@
 .. _PySQLite: http://initd.org/projects/pysqlite
 .. _Firebird: http://firebird.sourceforge.net
 .. _kinterbasdb: http://kinterbasdb.sourceforge.net/
-.. _Sybase: http://www.object-craft.com.au/projects/sybase/
 .. _`MAX DB`: http://www.mysql.com/products/maxdb/
 .. _sapdb: http://www.sapdb.org/sapdbPython.html
+.. _Sybase: http://www.object-craft.com.au/projects/sybase/
 .. _`MSSQL Server`: http://www.microsoft.com/sql/
 .. _pymssql: http://pymssql.sourceforge.net/
 .. _FreeTDS: http://www.freetds.org/

[SQL-CVS] r1788 - SQLObject/branches/0.7-bugfix/docs

[<sub...@co...>]

Author: phd
Date: 2006-05-22 06:52:16 -0600 (Mon, 22 May 2006)
New Revision: 1788

Modified:
   SQLObject/branches/0.7-bugfix/docs/News.txt
   SQLObject/branches/0.7-bugfix/docs/SQLObject.txt
Log:
Recollected features and bug fixes for 0.7.1.


Modified: SQLObject/branches/0.7-bugfix/docs/News.txt
===================================================================
--- SQLObject/branches/0.7-bugfix/docs/News.txt	2006-05-19 15:40:50 UTC (rev 1787)
+++ SQLObject/branches/0.7-bugfix/docs/News.txt	2006-05-22 12:52:16 UTC (rev 1788)
@@ -10,14 +10,15 @@
 SQLObject 0.7.1
 ===============
 
+Features & Interface
+--------------------
+
 * Added support for psycopg2_
 
 .. _psycopg2: http://initd.org/projects/psycopg2
 
-* Added support for MSSQL_.
+* Added support for MSSQL.
 
-.. _MSSQL: SQLObject.html#ms-sql-server
-
 * Added ``TimeCol``.
 
 * ``RelatedJoin`` and ``SQLRelatedJoin`` objects have a
@@ -28,6 +29,36 @@
 
 * Implemented ``RLIKE`` (reguluar expression LIKE).
 
+Small Features
+--------------
+
+* Select over RelatedJoin.
+
+* SQLite foreign keys.
+
+* Postgres DB URIs with a non-default path to unix socket.
+
+* Allow the use of foreign keys in selects.
+
+* Implemented addColumn() for SQLite.
+
+* With PySQLite2 use encode()/decode() from PySQLite1 for BLOBCol if available; else use base64.
+
+Bug Fixes
+---------
+
+* Cull patch (clear cache).
+
+* .destroySelf() inside a transaction.
+
+* Synchronize main connection cache during transaction commit.
+
+* Ordering joins with NULLs.
+
+* Fixed bugs with plain/non-plain setters.
+
+* Lots of other bug fixes.
+
 SQLObject 0.7.0
 ===============
 

Modified: SQLObject/branches/0.7-bugfix/docs/SQLObject.txt
===================================================================
--- SQLObject/branches/0.7-bugfix/docs/SQLObject.txt	2006-05-19 15:40:50 UTC (rev 1787)
+++ SQLObject/branches/0.7-bugfix/docs/SQLObject.txt	2006-05-22 12:52:16 UTC (rev 1788)
@@ -45,8 +45,9 @@
 
 Currently SQLObject supports MySQL_ via MySQLdb_ aka MySQL-python,
 PostgreSQL_ via psycopg1_ or psycopg2_, SQLite_ via PySQLite_,
-Firebird_ via kinterbasdb_, Sybase via Sybase_, and
-`MAX DB`_ (also known as SAP DB) via sapdb_.
+Firebird_ via kinterbasdb_, `MAX DB`_ (also known as SAP DB) via sapdb_,
+Sybase via Sybase_, and `MSSQL Server`_ via pymssql_ (+ FreeTDS_) or
+ADODBAPI_ (Win32).
 
 .. _MySQL: http://mysql.com
 .. _MySQLdb: http://sourceforge.net/projects/mysql-python/
@@ -57,9 +58,13 @@
 .. _PySQLite: http://initd.org/projects/pysqlite
 .. _Firebird: http://firebird.sourceforge.net
 .. _kinterbasdb: http://kinterbasdb.sourceforge.net/
-.. _Sybase: http://www.object-craft.com.au/projects/sybase/
 .. _`MAX DB`: http://www.mysql.com/products/maxdb/
 .. _sapdb: http://www.sapdb.org/sapdbPython.html
+.. _Sybase: http://www.object-craft.com.au/projects/sybase/
+.. _`MSSQL Server`: http://www.microsoft.com/sql/
+.. _pymssql: http://pymssql.sourceforge.net/
+.. _FreeTDS: http://www.freetds.org/
+.. _ADODBAPI: http://adodbapi.sourceforge.net/
 
 Python 2.2 or higher is required.  SQLObject makes extensive use of
 new-style classes.

[SQL-CVS] r1787 - home/phd/SQLObject/paramstyles/sqlobject

[<sub...@co...>]

Author: phd
Date: 2006-05-19 09:40:50 -0600 (Fri, 19 May 2006)
New Revision: 1787

Modified:
   home/phd/SQLObject/paramstyles/sqlobject/col.py
Log:
Merged patches from the revisions 1784:1786 from the trunk

Modified: home/phd/SQLObject/paramstyles/sqlobject/col.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/col.py	2006-05-19 15:39:35 UTC (rev 1786)
+++ home/phd/SQLObject/paramstyles/sqlobject/col.py	2006-05-19 15:40:50 UTC (rev 1787)
@@ -47,7 +47,7 @@
     from mx import DateTime
 except ImportError:
     try:
-        import DateTime # old version of mxDateTime
+        import DateTime # old version of mxDateTime, or Zope's Version if we're running with Zope
     except ImportError:
         mxdatetime_available = False
     else:
@@ -60,7 +60,10 @@
 
 if mxdatetime_available:
     DateTimeType = type(DateTime.now())
-    TimeType = type(DateTime.Time())
+    if hasattr(DateTime, "Time"):
+        TimeType = type(DateTime.Time())
+    else: # Zope
+        TimeType = type(DateTime.DateTime.Time(DateTime.DateTime()))
 
 if datetime_available:
     default_datetime_implementation = DATETIME_IMPLEMENTATION