sqlobject-cvs Mailing List for SQLObject (Page 124)
SQLObject is a Python ORM.
Brought to you by:
ianbicking,
phd
Menu
▾
▴
sqlobject-cvs — CVS notification
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(9) |
Apr
(74) |
May
(29) |
Jun
(16) |
Jul
(28) |
Aug
(10) |
Sep
(57) |
Oct
(9) |
Nov
(29) |
Dec
(12) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(7) |
Feb
(14) |
Mar
(6) |
Apr
(3) |
May
(12) |
Jun
(34) |
Jul
(9) |
Aug
(29) |
Sep
(22) |
Oct
(2) |
Nov
(15) |
Dec
(52) |
| 2005 |
Jan
(47) |
Feb
(78) |
Mar
(14) |
Apr
(35) |
May
(33) |
Jun
(16) |
Jul
(26) |
Aug
(63) |
Sep
(40) |
Oct
(96) |
Nov
(96) |
Dec
(123) |
| 2006 |
Jan
(159) |
Feb
(144) |
Mar
(64) |
Apr
(31) |
May
(88) |
Jun
(48) |
Jul
(16) |
Aug
(64) |
Sep
(87) |
Oct
(92) |
Nov
(56) |
Dec
(76) |
| 2007 |
Jan
(94) |
Feb
(103) |
Mar
(126) |
Apr
(123) |
May
(85) |
Jun
(11) |
Jul
(130) |
Aug
(47) |
Sep
(65) |
Oct
(70) |
Nov
(12) |
Dec
(11) |
| 2008 |
Jan
(30) |
Feb
(55) |
Mar
(88) |
Apr
(20) |
May
(50) |
Jun
|
Jul
(38) |
Aug
(1) |
Sep
(9) |
Oct
(5) |
Nov
(6) |
Dec
(39) |
| 2009 |
Jan
(8) |
Feb
(16) |
Mar
(3) |
Apr
(33) |
May
(44) |
Jun
(1) |
Jul
(10) |
Aug
(33) |
Sep
(74) |
Oct
(22) |
Nov
|
Dec
(15) |
| 2010 |
Jan
(28) |
Feb
(22) |
Mar
(46) |
Apr
(29) |
May
(1) |
Jun
(1) |
Jul
(27) |
Aug
(8) |
Sep
(5) |
Oct
(33) |
Nov
(24) |
Dec
(41) |
| 2011 |
Jan
(4) |
Feb
(12) |
Mar
(35) |
Apr
(29) |
May
(19) |
Jun
(16) |
Jul
(32) |
Aug
(25) |
Sep
(5) |
Oct
(11) |
Nov
(21) |
Dec
(12) |
| 2012 |
Jan
(3) |
Feb
(4) |
Mar
(20) |
Apr
(4) |
May
(25) |
Jun
(13) |
Jul
|
Aug
|
Sep
(2) |
Oct
(25) |
Nov
(9) |
Dec
(1) |
| 2013 |
Jan
(6) |
Feb
(8) |
Mar
|
Apr
(10) |
May
(31) |
Jun
(7) |
Jul
(18) |
Aug
(33) |
Sep
(4) |
Oct
(16) |
Nov
|
Dec
(27) |
| 2014 |
Jan
(2) |
Feb
|
Mar
|
Apr
(11) |
May
(39) |
Jun
(8) |
Jul
(11) |
Aug
(4) |
Sep
|
Oct
(27) |
Nov
|
Dec
(71) |
| 2015 |
Jan
(17) |
Feb
(47) |
Mar
(33) |
Apr
|
May
|
Jun
(9) |
Jul
(7) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(8) |
| 2016 |
Jan
(4) |
Feb
(4) |
Mar
|
Apr
|
May
(12) |
Jun
(7) |
Jul
(9) |
Aug
(31) |
Sep
(8) |
Oct
(3) |
Nov
(15) |
Dec
(1) |
| 2017 |
Jan
(13) |
Feb
(7) |
Mar
(14) |
Apr
(8) |
May
(10) |
Jun
(4) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(8) |
Nov
(4) |
Dec
(5) |
| 2018 |
Jan
(2) |
Feb
(8) |
Mar
|
Apr
(4) |
May
|
Jun
(6) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2019 |
Jan
(1) |
Feb
(16) |
Mar
(1) |
Apr
(3) |
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
(1) |
Dec
(3) |
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(2) |
Nov
|
Dec
(2) |
| 2021 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(6) |
Oct
(1) |
Nov
(1) |
Dec
(4) |
| 2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(3) |
Sep
(2) |
Oct
(2) |
Nov
(4) |
Dec
|
| 2024 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(9) |
| 2025 |
Jan
|
Feb
(4) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
(2) |
|
From: SourceForge.net <no...@so...> - 2006-08-15 12:45:42
|
Patches item #1516675, was opened at 2006-07-04 03:36 Message generated for change (Comment added) made by phd 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: Closed >Resolution: Fixed Priority: 5 Submitted By: Pau Aliagas (linux4u) >Assigned to: Oleg Broytmann (phd) 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. ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-08-15 16:45 Message: Logged In: YES user_id=4799 Well... I have created a test myself, applied the patch and committed in the revision 1859 to the trunk, rev. 1860 to the 0.7-branch. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1516675&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-14 11:04:24
|
Bugs item #1539927, was opened at 2006-08-14 04:04 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=1539927&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: Cannot create column with reserved word Initial Comment: It's a complement to #1533607 You can't create columns with reserved words, like `natural`, `index`. Column names should get a backtick. If anyone's interested, I'm making a patch. Mail-me at bernardojts AT gmail DOT com ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1539927&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-12 21:42:52
|
Patches item #1539325, was opened at 2006-08-12 14:42 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=1539325&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: Arlo Belshee (abelcodemonk) Assigned to: Nobody/Anonymous (nobody) Summary: fromDatabase and delColumn for sqlite Initial Comment: This patch implements both fromDatabase and delColumn for sqlite. I added sqlite to the appropriate existing tests; it passes them. fromDatabase is done by parsing the table creation sql from the sqlite_master table. This will work with any sqlite 3, and I think dates back into sqlite 2, but I'm not sure. delColumn is implemented by renaming the table, creating a new table without the one column, then copying all the data over. This is obviously not as efficient as on DBs that support drop column directly, but it works. This implementation of dropColumn does deal correctly with triggers, foreign keys, and indices that reference the table whose column is being dropped. It does not deal correctly with triggers & indices attached directly to the table being altered. Attached items will be lost. Extending the implementation to support re-creating those indices & triggers should be straightforward, but is beyond my needs. You are welcome to do so. Finally, this patch slightly improves the implementation of addColumn for sqlite. It performs a vacuum operation after each column add. See the sqlite documentation for why this is a good idea. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1539325&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-12 06:31:30
|
Bugs item #1539087, was opened at 2006-08-12 15:31 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=1539087&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: [N/A] (ymasuda) Assigned to: Nobody/Anonymous (nobody) Summary: Link to Japanese translation has moved Initial Comment: Hello, I have moved Japanese translation of SQLObject main doc from http://www.python.jp/~ymasuda/sqlobject/SQLObject.html which is listed on http://sqlobject.org/links.html, to http://ymasuda.jp/python/ sqlobject/doc_0.7/SQLObject.html . Also I'm going underway to translate all doc entries. These will be available at http://ymasuda.jp/python/sqlobject/doc_0.7/ . If you have any questions or advices, please tell me. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1539087&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-11 14:55:35
|
Patches item #1535941, was opened at 2006-08-07 16:56 Message generated for change (Comment added) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&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: Eddie (eddie0uk) Assigned to: Oleg Broytmann (phd) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-08-11 18:55 Message: Logged In: YES user_id=4799 ok ---------------------------------------------------------------------- Comment By: Eddie (eddie0uk) Date: 2006-08-11 18:18 Message: Logged In: YES user_id=1570436 Yeah, no semicolons. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-11 18:07 Message: Logged In: YES user_id=4799 Well, it is better than nothing. Thank you! Applied in the revision 1852 to the trunk, rev. 1853 to the 0.7-branch. PS. Are you sure there is no need for semicolons: SET ROWCOUNT %i; %s; SET ROWCOUNT 0 ??? ---------------------------------------------------------------------- Comment By: Eddie (eddie0uk) Date: 2006-08-09 19:24 Message: Logged In: YES user_id=1570436 Not that I am aware of. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-09 19:20 Message: Logged In: YES user_id=4799 You do not use "start" parameter. Do Sybase has a notion of offset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-11 14:18:22
|
Patches item #1535941, was opened at 2006-08-07 12:56 Message generated for change (Comment added) made by eddie0uk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&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: Accepted Priority: 5 Submitted By: Eddie (eddie0uk) Assigned to: Oleg Broytmann (phd) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- >Comment By: Eddie (eddie0uk) Date: 2006-08-11 14:18 Message: Logged In: YES user_id=1570436 Yeah, no semicolons. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-11 14:07 Message: Logged In: YES user_id=4799 Well, it is better than nothing. Thank you! Applied in the revision 1852 to the trunk, rev. 1853 to the 0.7-branch. PS. Are you sure there is no need for semicolons: SET ROWCOUNT %i; %s; SET ROWCOUNT 0 ??? ---------------------------------------------------------------------- Comment By: Eddie (eddie0uk) Date: 2006-08-09 15:24 Message: Logged In: YES user_id=1570436 Not that I am aware of. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-09 15:20 Message: Logged In: YES user_id=4799 You do not use "start" parameter. Do Sybase has a notion of offset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-11 14:07:44
|
Patches item #1535941, was opened at 2006-08-07 16:56 Message generated for change (Comment added) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&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: Accepted Priority: 5 Submitted By: Eddie (eddie0uk) >Assigned to: Oleg Broytmann (phd) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-08-11 18:07 Message: Logged In: YES user_id=4799 Well, it is better than nothing. Thank you! Applied in the revision 1852 to the trunk, rev. 1853 to the 0.7-branch. PS. Are you sure there is no need for semicolons: SET ROWCOUNT %i; %s; SET ROWCOUNT 0 ??? ---------------------------------------------------------------------- Comment By: Eddie (eddie0uk) Date: 2006-08-09 19:24 Message: Logged In: YES user_id=1570436 Not that I am aware of. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-09 19:20 Message: Logged In: YES user_id=4799 You do not use "start" parameter. Do Sybase has a notion of offset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-11 14:02:31
|
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: Closed >Resolution: Accepted Priority: 5 Submitted By: Neil Muller (nitwit) >Assigned to: Oleg Broytmann (phd) 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-08-11 18:02 Message: Logged In: YES user_id=4799 Applied and committed in the revision 1850 to the trunk, rev.1851 to the 0.7-branch.Thank you! ---------------------------------------------------------------------- Comment By: Neil Muller (nitwit) Date: 2006-06-25 15: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 17: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 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 |
|
From: SourceForge.net <no...@so...> - 2006-08-09 15:24:37
|
Patches item #1535941, was opened at 2006-08-07 12:56 Message generated for change (Comment added) made by eddie0uk You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&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: Eddie (eddie0uk) Assigned to: Nobody/Anonymous (nobody) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- >Comment By: Eddie (eddie0uk) Date: 2006-08-09 15:24 Message: Logged In: YES user_id=1570436 Not that I am aware of. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2006-08-09 15:20 Message: Logged In: YES user_id=4799 You do not use "start" parameter. Do Sybase has a notion of offset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-09 15:20:06
|
Patches item #1535941, was opened at 2006-08-07 16:56 Message generated for change (Comment added) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&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: Eddie (eddie0uk) Assigned to: Nobody/Anonymous (nobody) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-08-09 19:20 Message: Logged In: YES user_id=4799 You do not use "start" parameter. Do Sybase has a notion of offset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-09 15:16:21
|
Patches item #1524615, was opened at 2006-07-18 19:38 Message generated for change (Settings changed) made by phd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1524615&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: Luke Opperman (luke_opperman) >Assigned to: Oleg Broytmann (phd) Summary: Transaction.commit(close=True) fails to synchronize deletes Initial Comment: With close=True, Transaction.commit() calls _makeObsolete before synchronizing the main connection cache - this resets Transaction._deletedCache, so objects deleted in the transaction are never expired. Test and fix below: Index: dbconnection.py =================================================================== --- dbconnection.py (revision 1827) +++ dbconnection.py (working copy) @@ -837,8 +837,6 @@ if self._dbConnection.debug: self._dbConnection.printDebug(self._connection, '', 'COMMIT') self._connection.commit() - if close: - self._makeObsolete() subCaches = [(sub[0], sub[1].allIDs()) for sub in self.cache.allSubCachesByClassNames().items()] subCaches.extend([(x[0], x[1]) for x in self._deletedCache.items()]) for cls, ids in subCaches: @@ -846,6 +844,8 @@ inst = self._dbConnection.cache.tryGetByName(id, cls) if inst is not None: inst.expire() + if close: + self._makeObsolete() def rollback(self): if self._obsolete: Index: tests/test_transactions.py =================================================================== --- tests/test_transactions.py (revision 1827) +++ tests/test_transactions.py (working copy) @@ -52,7 +52,7 @@ finally: TestSOTrans._connection.autoCommit = True -def test_transaction_delete(): +def test_transaction_delete(close=False): if not supports('transactions'): return setupClass(TestSOTrans) @@ -63,5 +63,14 @@ bIn.destroySelf() bOut = TestSOTrans.select(TestSOTrans.q.name=='bob') assert bOut.count() == 1 + bOutInst = bOut[0] + bOutID = bOutInst.id + trans.commit(close=close) + assert bOut.count() == 0 + raises(SQLObjectNotFound, "TestSOTrans.get(bOutID)") + raises(SQLObjectNotFound, "bOutInst.name") finally: TestSOTrans._connection.autoCommit = True + +def test_transaction_delete_with_close(): + test_transaction_delete(close=True) ---------------------------------------------------------------------- >Comment By: Oleg Broytmann (phd) Date: 2006-08-09 19:16 Message: Logged In: YES user_id=4799 Applied at rev. 1840. Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1524615&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-08-09 15:02:36
|
Patches item #1512887, was opened at 2006-06-26 22:22 Message generated for change (Comment added) made by phd 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: Closed >Resolution: Accepted Priority: 5 Submitted By: Nobody/Anonymous (nobody) >Assigned to: Oleg Broytmann (phd) 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: Oleg Broytmann (phd) Date: 2006-08-09 19:02 Message: Logged In: YES user_id=4799 Applied at rev. 1847. Thank you. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-26 22: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 |
|
From: SourceForge.net <no...@so...> - 2006-08-07 12:56:46
|
Patches item #1535941, was opened at 2006-08-07 12:56 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=1535941&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: Eddie (eddie0uk) Assigned to: Nobody/Anonymous (nobody) Summary: Sybase and LIMIT Initial Comment: In SybaseConnection it reads: def _queryAddLimitOffset(self, query, start, end): # XXX Sybase doesn't support LIMIT return query Sybase does support LIMIT. I suggest having something like: def _queryAddLimitOffset(self, query, start, end): if end: return "SET ROWCOUNT %i %s SET ROWCOUNT 0" % (end, query) return query Cheers, eddie ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1535941&group_id=74338 |
|
From: <sub...@co...> - 2006-08-04 15:09:58
|
Author: phd
Date: 2006-08-04 09:09:48 -0600 (Fri, 04 Aug 2006)
New Revision: 1846
Modified:
home/phd/SQLObject/paramstyles/sqlobject/dbconnection.py
home/phd/SQLObject/paramstyles/sqlobject/tests/test_transactions.py
Log:
Merged patches from the revisions 1836:1845 from the trunk
Modified: home/phd/SQLObject/paramstyles/sqlobject/dbconnection.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/dbconnection.py 2006-08-04 04:04:45 UTC (rev 1845)
+++ home/phd/SQLObject/paramstyles/sqlobject/dbconnection.py 2006-08-04 15:09:48 UTC (rev 1846)
@@ -798,12 +798,14 @@
class Transaction(object):
def __init__(self, dbConnection):
- self._obsolete = False
+ # this is to skip __del__ in case of an exception in this __init__
+ self._obsolete = True
self._dbConnection = dbConnection
self._connection = dbConnection.getConnection()
self._dbConnection._setAutoCommit(self._connection, 0)
self.cache = CacheSet(cache=dbConnection.doCache)
self._deletedCache = {}
+ self._obsolete = False
def assertActive(self):
assert not self._obsolete, "This transaction has already gone through ROLLBACK; begin another transaction"
@@ -850,8 +852,6 @@
if self._dbConnection.debug:
self._dbConnection.printDebug(self._connection, '', 'COMMIT')
self._connection.commit()
- if close:
- self._makeObsolete()
subCaches = [(sub[0], sub[1].allIDs()) for sub in self.cache.allSubCachesByClassNames().items()]
subCaches.extend([(x[0], x[1]) for x in self._deletedCache.items()])
for cls, ids in subCaches:
@@ -859,6 +859,8 @@
inst = self._dbConnection.cache.tryGetByName(id, cls)
if inst is not None:
inst.expire()
+ if close:
+ self._makeObsolete()
def rollback(self):
if self._obsolete:
Modified: home/phd/SQLObject/paramstyles/sqlobject/tests/test_transactions.py
===================================================================
--- home/phd/SQLObject/paramstyles/sqlobject/tests/test_transactions.py 2006-08-04 04:04:45 UTC (rev 1845)
+++ home/phd/SQLObject/paramstyles/sqlobject/tests/test_transactions.py 2006-08-04 15:09:48 UTC (rev 1846)
@@ -52,7 +52,7 @@
finally:
TestSOTrans._connection.autoCommit = True
-def test_transaction_delete():
+def test_transaction_delete(close=False):
if not supports('transactions'):
return
setupClass(TestSOTrans)
@@ -63,5 +63,14 @@
bIn.destroySelf()
bOut = TestSOTrans.select(TestSOTrans.q.name=='bob')
assert bOut.count() == 1
+ bOutInst = bOut[0]
+ bOutID = bOutInst.id
+ trans.commit(close=close)
+ assert bOut.count() == 0
+ raises(SQLObjectNotFound, "TestSOTrans.get(bOutID)")
+ raises(SQLObjectNotFound, "bOutInst.name")
finally:
TestSOTrans._connection.autoCommit = True
+
+def test_transaction_delete_with_close():
+ test_transaction_delete(close=True)
|
|
From: SourceForge.net <no...@so...> - 2006-08-03 03:00:13
|
Bugs item #1533607, was opened at 2006-08-02 22:00 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=1533607&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: Adam Young (youngad6) Assigned to: Nobody/Anonymous (nobody) Summary: cannot create table with reserved word Initial Comment: Examples would be "group" or "order". All table names should be encased in backticks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1533607&group_id=74338 |
|
From: <sub...@co...> - 2006-08-02 14:40:49
|
Author: phd
Date: 2006-08-02 08:40:47 -0600 (Wed, 02 Aug 2006)
New Revision: 1840
Modified:
SQLObject/trunk/sqlobject/dbconnection.py
SQLObject/trunk/sqlobject/tests/test_transactions.py
Log:
A patch by Luke Opperman <lu...@me...> to fix problems with
transaction.commit(close=True).
Modified: SQLObject/trunk/sqlobject/dbconnection.py
===================================================================
--- SQLObject/trunk/sqlobject/dbconnection.py 2006-08-02 14:31:45 UTC (rev 1839)
+++ SQLObject/trunk/sqlobject/dbconnection.py 2006-08-02 14:40:47 UTC (rev 1840)
@@ -839,8 +839,6 @@
if self._dbConnection.debug:
self._dbConnection.printDebug(self._connection, '', 'COMMIT')
self._connection.commit()
- if close:
- self._makeObsolete()
subCaches = [(sub[0], sub[1].allIDs()) for sub in self.cache.allSubCachesByClassNames().items()]
subCaches.extend([(x[0], x[1]) for x in self._deletedCache.items()])
for cls, ids in subCaches:
@@ -848,6 +846,8 @@
inst = self._dbConnection.cache.tryGetByName(id, cls)
if inst is not None:
inst.expire()
+ if close:
+ self._makeObsolete()
def rollback(self):
if self._obsolete:
Modified: SQLObject/trunk/sqlobject/tests/test_transactions.py
===================================================================
--- SQLObject/trunk/sqlobject/tests/test_transactions.py 2006-08-02 14:31:45 UTC (rev 1839)
+++ SQLObject/trunk/sqlobject/tests/test_transactions.py 2006-08-02 14:40:47 UTC (rev 1840)
@@ -52,7 +52,7 @@
finally:
TestSOTrans._connection.autoCommit = True
-def test_transaction_delete():
+def test_transaction_delete(close=False):
if not supports('transactions'):
return
setupClass(TestSOTrans)
@@ -63,5 +63,14 @@
bIn.destroySelf()
bOut = TestSOTrans.select(TestSOTrans.q.name=='bob')
assert bOut.count() == 1
+ bOutInst = bOut[0]
+ bOutID = bOutInst.id
+ trans.commit(close=close)
+ assert bOut.count() == 0
+ raises(SQLObjectNotFound, "TestSOTrans.get(bOutID)")
+ raises(SQLObjectNotFound, "bOutInst.name")
finally:
TestSOTrans._connection.autoCommit = True
+
+def test_transaction_delete_with_close():
+ test_transaction_delete(close=True)
|
|
From: <sub...@co...> - 2006-08-02 14:31:47
|
Author: phd
Date: 2006-08-02 08:31:45 -0600 (Wed, 02 Aug 2006)
New Revision: 1839
Modified:
SQLObject/branches/0.7-bugfix/sqlobject/dbconnection.py
Log:
A patch by Dan Pascu <da...@ag...> to fix problems
with transaction.__del__() if there was an exception in __init__().
Modified: SQLObject/branches/0.7-bugfix/sqlobject/dbconnection.py
===================================================================
--- SQLObject/branches/0.7-bugfix/sqlobject/dbconnection.py 2006-08-02 14:31:28 UTC (rev 1838)
+++ SQLObject/branches/0.7-bugfix/sqlobject/dbconnection.py 2006-08-02 14:31:45 UTC (rev 1839)
@@ -733,12 +733,14 @@
class Transaction(object):
def __init__(self, dbConnection):
- self._obsolete = False
+ # this is to skip __del__ in case of an exception in this __init__
+ self._obsolete = True
self._dbConnection = dbConnection
self._connection = dbConnection.getConnection()
self._dbConnection._setAutoCommit(self._connection, 0)
self.cache = CacheSet(cache=dbConnection.doCache)
self._deletedCache = {}
+ self._obsolete = False
def assertActive(self):
assert not self._obsolete, "This transaction has already gone through ROLLBACK; begin another transaction"
|
|
From: <sub...@co...> - 2006-08-02 14:31:33
|
Author: phd
Date: 2006-08-02 08:31:28 -0600 (Wed, 02 Aug 2006)
New Revision: 1838
Modified:
SQLObject/trunk/sqlobject/dbconnection.py
Log:
A patch by Dan Pascu <da...@ag...> to fix problems
with transaction.__del__() if there was an exception in __init__().
Modified: SQLObject/trunk/sqlobject/dbconnection.py
===================================================================
--- SQLObject/trunk/sqlobject/dbconnection.py 2006-08-01 18:31:26 UTC (rev 1837)
+++ SQLObject/trunk/sqlobject/dbconnection.py 2006-08-02 14:31:28 UTC (rev 1838)
@@ -785,12 +785,14 @@
class Transaction(object):
def __init__(self, dbConnection):
- self._obsolete = False
+ # this is to skip __del__ in case of an exception in this __init__
+ self._obsolete = True
self._dbConnection = dbConnection
self._connection = dbConnection.getConnection()
self._dbConnection._setAutoCommit(self._connection, 0)
self.cache = CacheSet(cache=dbConnection.doCache)
self._deletedCache = {}
+ self._obsolete = False
def assertActive(self):
assert not self._obsolete, "This transaction has already gone through ROLLBACK; begin another transaction"
|
|
From: SourceForge.net <no...@so...> - 2006-07-18 15:38:28
|
Patches item #1524615, was opened at 2006-07-18 10:38 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=1524615&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: Luke Opperman (luke_opperman) Assigned to: Nobody/Anonymous (nobody) Summary: Transaction.commit(close=True) fails to synchronize deletes Initial Comment: With close=True, Transaction.commit() calls _makeObsolete before synchronizing the main connection cache - this resets Transaction._deletedCache, so objects deleted in the transaction are never expired. Test and fix below: Index: dbconnection.py =================================================================== --- dbconnection.py (revision 1827) +++ dbconnection.py (working copy) @@ -837,8 +837,6 @@ if self._dbConnection.debug: self._dbConnection.printDebug(self._connection, '', 'COMMIT') self._connection.commit() - if close: - self._makeObsolete() subCaches = [(sub[0], sub[1].allIDs()) for sub in self.cache.allSubCachesByClassNames().items()] subCaches.extend([(x[0], x[1]) for x in self._deletedCache.items()]) for cls, ids in subCaches: @@ -846,6 +844,8 @@ inst = self._dbConnection.cache.tryGetByName(id, cls) if inst is not None: inst.expire() + if close: + self._makeObsolete() def rollback(self): if self._obsolete: Index: tests/test_transactions.py =================================================================== --- tests/test_transactions.py (revision 1827) +++ tests/test_transactions.py (working copy) @@ -52,7 +52,7 @@ finally: TestSOTrans._connection.autoCommit = True -def test_transaction_delete(): +def test_transaction_delete(close=False): if not supports('transactions'): return setupClass(TestSOTrans) @@ -63,5 +63,14 @@ bIn.destroySelf() bOut = TestSOTrans.select(TestSOTrans.q.name=='bob') assert bOut.count() == 1 + bOutInst = bOut[0] + bOutID = bOutInst.id + trans.commit(close=close) + assert bOut.count() == 0 + raises(SQLObjectNotFound, "TestSOTrans.get(bOutID)") + raises(SQLObjectNotFound, "bOutInst.name") finally: TestSOTrans._connection.autoCommit = True + +def test_transaction_delete_with_close(): + test_transaction_delete(close=True) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1524615&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-07-17 15:02:17
|
Bugs item #1523898, was opened at 2006-07-17 17:02 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=1523898&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: Lutz Paelike (tremolo) Assigned to: Nobody/Anonymous (nobody) Summary: wrong parameter 'connect_time' of MySQLConnection Initial Comment: Due to a documentation bug of the MySQLdb project, sqlobject as inherited the following bug: The keyword parameter 'connect_timeout' of the constructor of the class MySQLConnection is wrongly documented as 'connect_time' in the docstring of MySQLdb.connections.MySQLConnection. The docstring of the C-Extension correctly documents it as 'connect_timeout' though. As a result the parameter is not correctly extracted from the keyword arguments dict and passed to MySQLdb. Fix: rename the parameter 'connect_time' to 'connect_timeout' in mysqlconnection.py (line 30) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1523898&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-07-14 12:28:11
|
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: Closed 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-14 14:28 Message: Logged In: YES user_id=553904 http://sourceforge.net/tracker/index.php?func=detail&aid=1521274&group_id=22307&atid=374932 makes is clear that it is a bug in the MySQLdb 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 |
|
From: SourceForge.net <no...@so...> - 2006-07-14 07:44:33
|
Bugs item #1522366, was opened at 2006-07-14 00:34 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1522366&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: No intermidiate table crated with one way RelatedJoin Initial Comment: I'm using SQLObject-0.7.1dev_r1675-py2.4.egg with Turbogears 0.9a6 When running tg-admin sql (sql|create) I get notice the following misfeature: RelatedJoin intermediate tables are only created when the table with the "lowest sorted" name is processed even if only the "highest sorted" name has a RelatedJoin. class File(SQLObject): filename = UnicodeCol() fileType = StringCol() sha1HexDigest = StringCol(length=40, alternateID=True) # NO related join here! class Project(SQLObject, HelperClassNotSqlObject): class sqlmeta: # Force SQLObject to create the intermediate # project_dumb_file table when looking at our project # files RelationalJoin instead of waiting to # create it until it finds the projects RelationalJoin # in DumbFile (which dows not exist). Our table must # be lexiographically smaller than DumbFile # a < d -> aproject < dumb_file table = "aproject" _defaultOrder = 'projectNumber' projectNumber = StringCol() files = RelatedJoin("File") description = UnicodeCol(default="") I do not want a relation from file to project because many classes has files and I do not want File to have relations to all these classes when looking at classes related to a file is not needed but looking at files related to a project is wery much needed. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-07-14 00:44 Message: Logged In: NO Okay, it seems I was optimistic when renaming only the table. Actually the class has to be renamed, but this breaks with the following error: Traceback (most recent call last): File "c:\Python24\Scripts\tg-admin-script.py", line 7, in ? sys.exit( File "c:\python24\lib\site-packages\TurboGears-0.9a6-py2.4.egg\turbogears\command\base.py", line 275, in main command.run() File "c:\python24\lib\site-packages\TurboGears-0.9a6-py2.4.egg\turbogears\command\base.py", line 134, in run command.the_runner.run(sys.argv) File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\manager\command.py", line 102, in run runner.run() File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\manager\command.py", line 233, in run self.command() File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\manager\command.py", line 508, in command print cls.createTableSQL().strip() + ';\n' File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\main.py", line 1336, in createTableSQL sql += '\n' + cls.createJoinTablesSQL(connection=conn) File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\main.py", line 1357, in createJoinTablesSQL for join in cls._getJoinsToCreate(): File "c:\python24\lib\site-packages\SQLObject-0.7.1dev_r1675-py2.4.egg\sqlobject\main.py", line 1390, in _getJoinsToCreate if join.soClass.__name__ > join.otherClass.__name__: AttributeError: 'SORelatedJoin' object has no attribute 'otherClass' And, I have no intention of renaming Project to aProject anyway ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1522366&group_id=74338 |
|
From: SourceForge.net <no...@so...> - 2006-07-14 07:34:03
|
Bugs item #1522366, was opened at 2006-07-14 00:34 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=1522366&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: No intermidiate table crated with one way RelatedJoin Initial Comment: I'm using SQLObject-0.7.1dev_r1675-py2.4.egg with Turbogears 0.9a6 When running tg-admin sql (sql|create) I get notice the following misfeature: RelatedJoin intermediate tables are only created when the table with the "lowest sorted" name is processed even if only the "highest sorted" name has a RelatedJoin. class File(SQLObject): filename = UnicodeCol() fileType = StringCol() sha1HexDigest = StringCol(length=40, alternateID=True) # NO related join here! class Project(SQLObject, HelperClassNotSqlObject): class sqlmeta: # Force SQLObject to create the intermediate # project_dumb_file table when looking at our project # files RelationalJoin instead of waiting to # create it until it finds the projects RelationalJoin # in DumbFile (which dows not exist). Our table must # be lexiographically smaller than DumbFile # a < d -> aproject < dumb_file table = "aproject" _defaultOrder = 'projectNumber' projectNumber = StringCol() files = RelatedJoin("File") description = UnicodeCol(default="") I do not want a relation from file to project because many classes has files and I do not want File to have relations to all these classes when looking at classes related to a file is not needed but looking at files related to a project is wery much needed. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540672&aid=1522366&group_id=74338 |
|
From: Esther B. <Est...@ma...> - 2006-07-11 09:43:28
|
splashed out since that time. There was only one thing that I didn't like.
gentle sea. A mile from shore a fishing boat chummed the water. and the
"Laboratory Assistant Schuhart," he says. "Official-and I stress
horizons out ahead for us all. He stepped forward.
|
|
From: manishapilu <ytm...@ho...> - 2006-07-11 02:09:59
|
<h| align="center">Univers1ty Degree</h1> <div al1gn="center"><br> OBTAIN A PROSPER0US FUTURE, MONEY-EARNING POWER,<BR>AND <acb></acb>THE PRESTIGE THAT COMES <acz></acz> WITH HAVING THE CAREER POSITION YOU'VE<BR>ALWAYS DREAMED OF. DIPLOMA FROM<BR>PRESTIGIOUS NON-ACCREDITED<BR>UNVERSITIES BASED ON YOUR PRESENT KNOWLEDGE AND PROFESSIONAL <acc></acc> EXPERIENCE.<br> <i><font size="4"><b><font size="5">If you qualify, no required tests, classes, books <acz></acz>or examinations.</font></b></font></i> <font size="5"><b><br> </b></font><br> <b><font size="5">Confidentiality Assured<br> </font></b><br> <font color="#FF0033" size="+2"><b>1-815-828-2222</b></font><br> 24 <acy></acy>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> Anyway, youd better go and get packed, <acx></acx>Harry, |
89 messages has been excluded from this view by a project administrator.
