sqlobject-cvs — CVS notification

[SQL-CVS] [ sqlobject-Bugs-1519914 ] Documentation error: DateTime should be DateTimeCol

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

Bugs item #1519914, was opened at 2006-07-10 05:36
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=1519914&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: Documentation error: DateTime should be DateTimeCol

Initial Comment:

On page:

 http://www.sqlobject.org/SQLObject.html

under the heading:

 Col Class: Specifying Columns

the text:

 DateTime.now

should be:

 DateTimeCol.now

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

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

[SQL-CVS] [ sqlobject-Bugs-1517116 ] Multiple join of table with itself fails with Postgres

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

Bugs item #1517116, was opened at 2006-07-04 20:55
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=1517116&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: Postgres
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Henrik Weber (hweber)
Assigned to: Nobody/Anonymous (nobody)
Summary: Multiple join of table with itself fails with Postgres

Initial Comment:
With SQLobject 0.7.0 using Postgres I have tried to 
join a table with itself more than once. The code 
looks something like this:

alias1 = Alias(Tbl, "T1")
alias2 = Alias(Tbl, "T2")

joins = [INNERJOINOn(Tbl, alias1, Tbl.q.tblid == 
alias1.q.tblid), INNERJOINOn(Tbl, alias2, Tbl.q.tblid 
== alias2.q.tblid)]

result = Tbl.select(somewherecrit, join=joins)

The resulting SQL statement looks like this:

SELECT Tbl.id, Tbl.tblid FROM Tbl INNER JOIN Tbl AS T1 
ON (Tbl.tblid = T2.tblid), Tbl INNER JOIN Tbl AS T2 ON 
(Tbl.tblid = T2.tblid)
WHERE ...

The resulting error message is:
psycopg2.ProgrammingError: table name "Tbl" specified 
more than once


The correct statement would actually have been:

SELECT Tbl.id, Tbl.tblid FROM Tbl INNER JOIN Tbl AS T1 
ON (Tbl.tblid = T2.tblid) INNER JOIN Tbl AS T2 ON 
(Tbl.tblid = T2.tblid)
WHERE ...

I tried defining the join recursively, but you can't 
use a Join object as parameter for a new join.

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

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

[SQL-CVS] [ sqlobject-Bugs-1516384 ] SQLbuilder aliases fail for Firebird

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

Bugs item #1516384, was opened at 2006-07-03 16:43
Message generated for change (Settings changed) made by hweber
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1516384&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: Firebird/Interbase
Group: SQLObject release (specify)
>Status: Deleted
Resolution: None
Priority: 5
Submitted By: Henrik Weber (hweber)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQLbuilder aliases fail for Firebird

Initial Comment:
Creating a table alias with SQLBuilder will alway 
create alias clauses of the form:

orig_table AS alias_name

SQLbuilder does not discriminate between different SQL 
dialects here.

For Firebird this syntax variant fails, because 
aliases are defined without the AS keyword there:

orig_table alias_name

The AS keyword will generate a syntax error with 
Firebird.

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

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

[SQL-CVS] [ sqlobject-Bugs-1516394 ] SQLbuilder aliases fail for Firebird

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

Bugs item #1516394, was opened at 2006-07-03 16:56
Message generated for change (Comment added) made by hweber
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1516394&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: Firebird/Interbase
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Henrik Weber (hweber)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQLbuilder aliases fail for Firebird

Initial Comment:
Creating a table alias with SQLBuilder will alway 
create alias clauses of the form:

orig_table AS alias_name

SQLbuilder does not discriminate between different SQL 
dialects here.

For Firebird this syntax variant fails, because 
aliases are defined without the AS keyword there:

orig_table alias_name

The AS keyword will generate a syntax error with 
Firebird.

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

>Comment By: Henrik Weber (hweber)
Date: 2006-07-04 20:37

Message:
Logged In: YES 
user_id=121229

Forgot to mention: this is with SQLobject 0.7.0

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

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

[SQL-CVS] [ sqlobject-Bugs-1517027 ] Exception when using new MySQLdb and UnicodeCol

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

Bugs item #1517027, was opened at 2006-07-04 18:01
Message generated for change (Comment added) made by markus_gritsch
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1517027&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: Markus Gritsch (markus_gritsch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Exception when using new MySQLdb and UnicodeCol

Initial Comment:
SQLObject-0.7.1b1-py2.4.egg
MySQL Server 5.0
Windows XP SP 2

MySQL-python.exe-1.2.0.win32-py2.4.zip
MySQL-python.exe-1.2.1_p2.win32-py2.4.exe

The attached test-script 'SQLObject_test.py' works only
when using MySQL-python.exe-1.2.0.win32-py2.4.zip, but
fails when using MySQL-python.exe-1.2.1_p2.win32-py2.4.exe.

The second attachment 'MySQLdb_test.py' which uses
MySQLdb directly, works with both versions of the
connector.

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

>Comment By: Markus Gritsch (markus_gritsch)
Date: 2006-07-04 18:11

Message:
Logged In: YES 
user_id=553904

Additional Note: Even if SQLObject can store the unicode
string in the DB (and can also retrieve it correctly) when
using MySQL-python.exe-1.2.0.win32-py2.4.zip, I think it is
stored incorrectly in the DB, because when looking at the
value with MySQL Query Browser, it is displayed containing
strange characters.

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

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

[SQL-CVS] [ sqlobject-Bugs-1517027 ] Exception when using new MySQLdb and UnicodeCol

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

Bugs item #1517027, was opened at 2006-07-04 18:01
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=1517027&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: Markus Gritsch (markus_gritsch)
Assigned to: Nobody/Anonymous (nobody)
Summary: Exception when using new MySQLdb and UnicodeCol

Initial Comment:
SQLObject-0.7.1b1-py2.4.egg
MySQL Server 5.0
Windows XP SP 2

MySQL-python.exe-1.2.0.win32-py2.4.zip
MySQL-python.exe-1.2.1_p2.win32-py2.4.exe

The attached test-script 'SQLObject_test.py' works only
when using MySQL-python.exe-1.2.0.win32-py2.4.zip, but
fails when using MySQL-python.exe-1.2.1_p2.win32-py2.4.exe.

The second attachment 'MySQLdb_test.py' which uses
MySQLdb directly, works with both versions of the
connector.

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

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

[SQL-CVS] [ sqlobject-Patches-1516675 ] multiple left join fix

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

Patches item #1516675, was opened at 2006-07-04 01:36
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=1516675&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: Pau Aliagas (linux4u)
Assigned to: Nobody/Anonymous (nobody)
Summary: multiple left join fix

Initial Comment:
I having problems trying to create a query with two
left joins as only one allows having the left table
specified, the rest have to be None, otherwise it
generates invalid SQL.

The theory is that if you don't specify the left table,
it joins agains the first table defined. In this case
you don't need a comma before the left join.

But if you want to define both tables (the recommended
procedure), you need a leading comma.

As it is now, you cannot mix them:
            if tables and join[0].table1:
                join_str = ", "
            else:
                join_str = ' '
            join_str += " ".join([self.sqlrepr(j) for j
in join])

As I propose, every joind is treated individually:

            join_str = ""
            for j in join:
                if tables and j.table1:
                    sep = ", "
                else:
                    sep = ' '
                join_str += sep + self.sqlrepr(j)

I attach the patch. I posted it in the mailing lisrt
without any reposnse.

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

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

[SQL-CVS] [ sqlobject-Bugs-1516394 ] SQLbuilder aliases fail for Firebird

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

Bugs item #1516394, was opened at 2006-07-03 16: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=1516394&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: Firebird/Interbase
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Henrik Weber (hweber)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQLbuilder aliases fail for Firebird

Initial Comment:
Creating a table alias with SQLBuilder will alway 
create alias clauses of the form:

orig_table AS alias_name

SQLbuilder does not discriminate between different SQL 
dialects here.

For Firebird this syntax variant fails, because 
aliases are defined without the AS keyword there:

orig_table alias_name

The AS keyword will generate a syntax error with 
Firebird.

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

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

[SQL-CVS] [ sqlobject-Bugs-1516384 ] SQLbuilder aliases fail for Firebird

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

Bugs item #1516384, was opened at 2006-07-03 16:43
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=1516384&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: Firebird/Interbase
Group: SQLObject release (specify)
Status: Open
Resolution: None
Priority: 5
Submitted By: Henrik Weber (hweber)
Assigned to: Nobody/Anonymous (nobody)
Summary: SQLbuilder aliases fail for Firebird

Initial Comment:
Creating a table alias with SQLBuilder will alway 
create alias clauses of the form:

orig_table AS alias_name

SQLbuilder does not discriminate between different SQL 
dialects here.

For Firebird this syntax variant fails, because 
aliases are defined without the AS keyword there:

orig_table alias_name

The AS keyword will generate a syntax error with 
Firebird.

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

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

[SQL-CVS] Obtain the career you have always wanted with the University Degree you deserve.

[criat <blb...@ho...>]

<h1 align="center">Univers1ty Degree</h|>
<div align="center"><br>
  OBT@IN A PROSPEROUS <acz></acz>FUTURE, MONEY-EARNING POWER,<BR>AND THE PRESTIGE THAT COMES 
  WITH HAVING <acu></acu>THE CAREER POSITION YOU'VE<BR>ALWAYS DREAMED OF. DIPLOMA FROM<BR>PRESTIGIOUS 
  NON-ACCREDITED<BR>UNVERSITIES BASED ON YOUR <acc></acc>PRESENT KNOWLEDGE AND PROFESSIONAL 
 <acu></acu> EXPERIENCE.<br>
  <i><font size="4"><b><font size="5">If you qualify, no required tests, classes, 
  books or <acd></acd>examinations.</font></b></font></i> <font size="5"><b><br>
  </b></font><br>
 <act></act> <b><font size="5">Confidentiality Assured<br>
  </font></b><br>
  <font color="#FF0033" size="+2"><b>1-815-828-2222</b></font><br>
 <acc></acc> 24 hours a day, 7 days a week including Sundays and Holidays<br>
</div><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR><BR> But hed make it up to her when she came back with the answers from S
irius,

 
 

[SQL-CVS] [ sqlobject-Patches-1512887 ] simple error by creating sql-code

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

Patches item #1512887, was opened at 2006-06-26 11:22
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1512887&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: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: simple error by creating sql-code

Initial Comment:
main.py

line 1389:

use
    sql += ';\n' + join_sql
instead of
    sql = ';\n' + join_sql


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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-06-26 11:27

Message:
Logged In: NO 

(I forget to say that I am using the svn-Revision 1827 of
sqlobject)

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

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

[SQL-CVS] [ sqlobject-Patches-1512887 ] simple error by creating sql-code

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

Patches item #1512887, was opened at 2006-06-26 11:22
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=1512887&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: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: simple error by creating sql-code

Initial Comment:
main.py

line 1389:

use
    sql += ';\n' + join_sql
instead of
    sql = ';\n' + join_sql


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

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

[SQL-CVS] [ sqlobject-Bugs-1512334 ] Missing character in 1421647 resolution

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

Bugs item #1512334, was opened at 2006-06-26 02:14
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=1512334&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 from repository
Status: Open
Resolution: None
Priority: 5
Submitted By: Roger Demetrescu (rogercd)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing character in 1421647 resolution

Initial Comment:
In the patch proposed for ticket 1421647, there was a
missing "+" character... It's my fault.

Sorry for the inconvenience. The attached patch should
correct it.



This was reported in
http://trac.turbogears.org/turbogears/ticket/1010. As
you can see, the author is also mentioning this:

============
Similar missing-character problems on lines 1441 (join
with '\n' instead of ';\n') and 1423 (same problem),
which result in not having semicolons to end the
statements.
============

I think he is refering to all those:
<code>
return '\n'.join(sql)
</code>

It worths taking a look...


Thanks

Roger Demetrescu

PS: Is there a way of reopening a ticket ? I couldn't
find any, so that's why I'm opening a new one.


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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1512334&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 (Comment added) made by nitwit
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: Neil Muller (nitwit)
Date: 2006-06-25 13:44

Message:
Logged In: YES 
user_id=698097

Updated patch uploaded.

Looking at the mysqldb code more closely shows I
misinterpreted charset in the previous patch. Charset is the
encoding used by the MySQL database. Thus I've added a
sqlobject_encoding field to the URI to allow specifying the
encoding before the conversion to unicode. 

For cases where charset is not set, and use_unicode is
false, it seems we still need to convert to unicode as
MySQLdb still expects to conver the query from unicode.



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

Comment By: Neil Muller (nitwit)
Date: 2006-06-07 15:11

Message:
Logged In: YES 
user_id=698097

In my test cases, mysqldb required that the queries be
unicode regardless of what use_unicode was set to, but I
haven't looked into this closely. I'll review the logic of
that carefully when I fix the other errors in the patch.


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

Comment By: Oleg Broytmann (phd)
Date: 2006-06-07 14: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] Hi, mid-term

[Rhoda C. <Rho...@ma...>]

Even if you have no erectin problems SOFT CIAzLIS 
would help you to make BETTER SE  X MORE OFTEN!
and to bring  unimagnable plesure to her.

Just disolve half a pil under your tongue 
and get ready for action in 15 minutes. 

The tests showed that the majority of men 
after taking this medic ation were able to have 
PERFECT ER ECTI ON during 36 hours!

VISIT US, AND GET OUR SPECIAL 70% DISC OUNT OFER!

http://dvpres.invadeshark.com/?62966377

==========
rule holds for us now, of course: we choose our next world through what we
hands of the International Institute."
gracks. "Why aren't there more of us here? Why, where I  came  from  there
In the very back of the garage, near the  canisters,  I could see  something
fiction  solely  with  girls  in  brass  brassieres being rescued  from  the
Zone you can either cry  or  joke--and I  never  cried, even  as  a child. I

well. They can help you bring the newcomers along."
     "What official sources?" I asked, and smiled like a fool myself.

[SQL-CVS] [ sqlobject-Bugs-1510525 ] Missing self. in index.py

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

Bugs item #1510525, was opened at 2006-06-22 12:45
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=1510525&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 from repository
Status: Open
Resolution: None
Priority: 5
Submitted By: Giuseppe Corbelli (cowo)
Assigned to: Nobody/Anonymous (nobody)
Summary: Missing self. in index.py

Initial Comment:
In 
sqlobject/index.py 
DatabaseIndex._get_name

def _get_name(self):
    return kw['name']

must become

def _get_name(self):
    return self.kw['name']


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

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

[SQL-CVS] [ sqlobject-Patches-1299109 ] Support FOREIGN KEY for MySQL

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

Patches item #1299109, was opened at 2005-09-22 13:46
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1299109&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: Accepted
Priority: 5
Submitted By: Andy Dustman (adustman)
Assigned to: Nobody/Anonymous (nobody)
Summary: Support FOREIGN KEY for MySQL

Initial Comment:
MySQL supports the full FOREIGN KEY syntax in versions
3.23.50 and newer, and 4.0.8 and newer, and I believe
all 4.1 and 5.0 versions. To implement this in
SQLObject-0.7a, I copied the
col.SOForeignKey.postgresCreateSQL() method to
mysqlCreateSQL() and performed some minor editing.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2006-06-19 12:05

Message:
Logged In: NO 

I had the same problem and fixed it almost the same way as 
the bug reporter, and it worked. I think this patch should 
be included as soon as possible. 

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

Comment By: Oleg Broytmann (phd)
Date: 2005-10-23 06:28

Message:
Logged In: YES 
user_id=4799

Applied at the revision 1135 in the trunk.

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

Comment By: Oleg Broytmann (phd)
Date: 2005-09-23 07:17

Message:
Logged In: YES 
user_id=4799

Looks good at first glance, but I am reluctant to apply such
a patch while SQLObject is at the beta stage, espcially
considering I use Postgres and MySQL, but not MySQL, so I
cannot properly test it. Let's wait until post-0.7.

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

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

[SQL-CVS] [ sqlobject-Bugs-1507767 ] StringCol(char_binary=True) breaks if DBMS!=MySQL

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

Bugs item #1507767, was opened at 2006-06-17 06:41
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=1507767&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: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: StringCol(char_binary=True) breaks if DBMS!=MySQL

Initial Comment:
StringCol(char_binary=True) is required by MySQL to
allow case-sensitive comparisons for that column.
However, for instance for SQLite this is not required.
In the latter case "char_binary=True" should be
ignored, but instead an exception is trown:
ValueError: SQLite does not support binary character
columns


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

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

[SQL-CVS] r1824 - SQLObject/branches/0.7-bugfix/sqlobject/mysql

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

Author: phd
Date: 2006-06-16 01:53:25 -0600 (Fri, 16 Jun 2006)
New Revision: 1824

Modified:
   SQLObject/branches/0.7-bugfix/sqlobject/mysql/mysqlconnection.py
Log:
client_encoding has not been set.


Modified: SQLObject/branches/0.7-bugfix/sqlobject/mysql/mysqlconnection.py
===================================================================
--- SQLObject/branches/0.7-bugfix/sqlobject/mysql/mysqlconnection.py	2006-06-16 01:32:59 UTC (rev 1823)
+++ SQLObject/branches/0.7-bugfix/sqlobject/mysql/mysqlconnection.py	2006-06-16 07:53:25 UTC (rev 1824)
@@ -136,7 +136,6 @@
             colClass, kw = self.guessClass(t)
             if self.kw['use_unicode'] and colClass is col.StringCol:
                 colClass = col.UnicodeCol
-                if self.client_encoding: kw['dbEncoding'] = self.client_encoding
             kw['name'] = soClass.sqlmeta.style.dbColumnToPythonAttr(field)
             kw['notNone'] = not nullAllowed
             if default and t.startswith('int'):

[SQL-CVS] r1823 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 19:32:59 -0600 (Thu, 15 Jun 2006)
New Revision: 1823

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
by: Hammy
Delete comment

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 01:32:40 UTC (rev 1822)
+++ SQLObject/docs/index.comments.txt	2006-06-16 01:32:59 UTC (rev 1823)
@@ -14,10 +14,3 @@
 username: MB
 
 Auch an unterschiedlichen Stellen geht das
-==== $(start) +++ c ++
-----------------------------------------
-date: 2006-06-15T19:31:40
-id: 4
-ip: 66.92.16.159
-
-This is a test.- we're- using- restructured- textwhich is good for *this*.

[SQL-CVS] r1822 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 19:32:40 -0600 (Thu, 15 Jun 2006)
New Revision: 1822

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
by: Hammy

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 01:31:42 UTC (rev 1821)
+++ SQLObject/docs/index.comments.txt	2006-06-16 01:32:40 UTC (rev 1822)
@@ -20,9 +20,4 @@
 id: 4
 ip: 66.92.16.159
 
-This is a test.
-- we're
-- using
-- restructured
-- text
-which is good for *this*.
+This is a test.- we're- using- restructured- textwhich is good for *this*.

[SQL-CVS] r1821 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 19:31:42 -0600 (Thu, 15 Jun 2006)
New Revision: 1821

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
Add comment

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 00:22:12 UTC (rev 1820)
+++ SQLObject/docs/index.comments.txt	2006-06-16 01:31:42 UTC (rev 1821)
@@ -14,3 +14,15 @@
 username: MB
 
 Auch an unterschiedlichen Stellen geht das
+==== $(start) +++ c ++
+----------------------------------------
+date: 2006-06-15T19:31:40
+id: 4
+ip: 66.92.16.159
+
+This is a test.
+- we're
+- using
+- restructured
+- text
+which is good for *this*.

[SQL-CVS] r1820 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 18:22:12 -0600 (Thu, 15 Jun 2006)
New Revision: 1820

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
Delete comment

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 00:21:57 UTC (rev 1819)
+++ SQLObject/docs/index.comments.txt	2006-06-16 00:22:12 UTC (rev 1820)
@@ -14,10 +14,3 @@
 username: MB
 
 Auch an unterschiedlichen Stellen geht das
-==== $(example)  c +++
-----------------------------------------
-date: 2006-04-14T22:41:40
-id: 5
-ip: 68.98.143.137
-
-testing

[SQL-CVS] r1819 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 18:21:57 -0600 (Thu, 15 Jun 2006)
New Revision: 1819

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
Delete comment

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 00:21:43 UTC (rev 1818)
+++ SQLObject/docs/index.comments.txt	2006-06-16 00:21:57 UTC (rev 1819)
@@ -1,11 +1,3 @@
-==== $(documentation)  c + c
-----------------------------------------
-date: 2006-01-31T06:41:48
-id: 1
-ip: 84.190.227.75
-username: MB
-
-Hier kann man Kommentare eingeben
 ==== $(example)  c
 ----------------------------------------
 date: 2006-01-31T06:42:16

[SQL-CVS] r1818 - SQLObject/docs

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

Author: ianb
Date: 2006-06-15 18:21:43 -0600 (Thu, 15 Jun 2006)
New Revision: 1818

Modified:
   SQLObject/docs/index.comments.txt
Log:
in page: http://pythonpaste.org/
Delete comment

Modified: SQLObject/docs/index.comments.txt
===================================================================
--- SQLObject/docs/index.comments.txt	2006-06-16 00:21:13 UTC (rev 1817)
+++ SQLObject/docs/index.comments.txt	2006-06-16 00:21:43 UTC (rev 1818)
@@ -22,14 +22,6 @@
 username: MB
 
 Auch an unterschiedlichen Stellen geht das
-==== $(start) +++ c
-----------------------------------------
-date: 2006-02-18T21:13:55
-id: 4
-ip: 216.80.121.210
-username: Adrian H.
-
-Just spamming this page with another tesxt! :)
 ==== $(example)  c +++
 ----------------------------------------
 date: 2006-04-14T22:41:40