sqlobject-discuss — All things SQLObject-related

Re: [SQLObject] SQLObject 1.6.0

[Gustavo A. D. <gus...@gm...>]

Hi!

Short question: SQLObject does not support Python V3 right?

Thanks!

2014-05-15 12:56 GMT-03:00 Oleg Broytman <ph...@ph...>:

> Hello!
>
> I'm pleased to announce version 1.6.0, the first stable release of branch
> 1.6 of SQLObject.
>
>
> What's new in SQLObject
> =======================
>
> Features & Interface
> --------------------
>
> * Python 2.4 is no longer supported. The minimal supported version is
>   Python 2.5.
>
> * Support for Python 2.5 is declared obsolete and will be removed
>   in the next release.
>
> * Upgrade ez_setup to 1.4.2.
>
> * Adapt duplicate error message strings for SQLite 3.8.
>
> Contributor for this release is Neil Muller.
>
> For a more complete list, please see the news:
> http://sqlobject.org/News.html
>
>
> What is SQLObject
> =================
>
> SQLObject is an object-relational mapper.  Your database tables are
> described
> as classes, and rows are instances of those classes.  SQLObject is meant
> to be
> easy to use and quick to get started with.
>
> SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
> Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).
>
>
> Where is SQLObject
> ==================
>
> Site:
> http://sqlobject.org
>
> Development:
> http://sqlobject.org/devel/
>
> Mailing list:
> https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss
>
> Archives:
> http://news.gmane.org/gmane.comp.python.sqlobject
>
> Download:
> https://pypi.python.org/pypi/SQLObject/1.6.0
>
> News and changes:
> http://sqlobject.org/News.html
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>



-- 

Gustavo A. Díaz

artistic.gdnet.com.ar

"Desarrollando un mundo Libre"

[SQLObject] SQLObject 2.0.0a2

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 2.0.0a2, the second alpha of the upcoming
release of branch 2.0 of SQLObject.


What's new in SQLObject
=======================

* Allow unicode in .orderBy(u'-column').

* PostgresConnection, when used with fromDatabase=True, set alternateID
  for unique columns.

* Upgrade ez_setup to 7.0.

Contributors for this release are Andrew Trusty and Jared Jennings.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.0.0a2dev-20141028

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.7.0b2

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.7.0b2, the second beta of the upcoming
release of branch 1.7 of SQLObject.


What's new in SQLObject
=======================

* Allow unicode in .orderBy(u'-column').

Contributor for this release is Andrew Trusty.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.7.0b2dev-20141026

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.6.1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.6.1, the first bugfix release of branch
1.6 of SQLObject.


What's new in SQLObject
=======================

* Allow unicode in .orderBy(u'-column').

Contributor for this release is Andrew Trusty.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.6.1

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.5.3

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.5.3, a bugfix release of branch
1.5 of SQLObject.


What's new in SQLObject
=======================

* Allow unicode in .orderBy(u'-column').

Contributor for this release is Andrew Trusty.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.5.3

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] orderBy isinstance str check

[Oleg B. <ph...@ph...>]

On Sat, Oct 25, 2014 at 12:42:32PM -0600, Andrew Trusty <at...@ga...> wrote:
> On Sat, Oct 25, 2014 at 12:09 PM, Oleg Broytman <ph...@ph...> wrote:
> 
> > > I recently discovered that some of my code was passing unicode strings to
> > > orderBy and that this worked as long as the strings didn't start with
> > "-".
> > > When they did start with "-", the _mungeOrderBy check (line 69 in
> > > sresults.py) didn't detect the "-" because the strings were of type
> > unicode
> > > and not type str and _mungeOrderBy checks for str and not basestring.
> > >
> >    If you replace 'str' with
> > 'basestring' in 'if isinstance(orderBy, str)' does it work for you?
> 
> Yes, that works for me.

   Ok, I'll fix that. Thank you for spotting! I'm going to release 1.5.3
and 1.6.1. What version are you using?

> I wasn't sure if that was the only change that was
> needed or if some of the other isinstance checks might need to be changed
> to check basestring as well.

   There are many occurrences of 'isinstance(x, str)' all over SQLObject
sources. You can try to fix them and test. I'll accept a patch or a pull
request and test it if you provide one.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] orderBy isinstance str check

[Andrew T. <at...@ga...>]

On Sat, Oct 25, 2014 at 12:09 PM, Oleg Broytman <ph...@ph...> wrote:

> > I recently discovered that some of my code was passing unicode strings to
> > orderBy and that this worked as long as the strings didn't start with
> "-".
> > When they did start with "-", the _mungeOrderBy check (line 69 in
> > sresults.py) didn't detect the "-" because the strings were of type
> unicode
> > and not type str and _mungeOrderBy checks for str and not basestring.
> >
> > I was just wondering if this was on purpose or not as it looks like there
> > are other places in the sqlobject code that do check for type basestring.
>
>    Certainly not. Just an oversight. If you replace 'str' with
> 'basestring' in 'if isinstance(orderBy, str)' does it work for you?
>

Yes, that works for me.  I wasn't sure if that was the only change that was
needed or if some of the other isinstance checks might need to be changed
to check basestring as well.

Re: [SQLObject] orderBy isinstance str check

[Oleg B. <ph...@ph...>]

Hi!

On Sat, Oct 25, 2014 at 11:52:37AM -0600, Andrew Trusty <at...@ga...> wrote:
> Hi,
> 
> I recently discovered that some of my code was passing unicode strings to
> orderBy and that this worked as long as the strings didn't start with "-".
> When they did start with "-", the _mungeOrderBy check (line 69 in
> sresults.py) didn't detect the "-" because the strings were of type unicode
> and not type str and _mungeOrderBy checks for str and not basestring.
> 
> I was just wondering if this was on purpose or not as it looks like there
> are other places in the sqlobject code that do check for type basestring.

   Certainly not. Just an oversight. If you replace 'str' with
'basestring' in 'if isinstance(orderBy, str)' does it work for you?

> Andrew

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] orderBy isinstance str check

[Andrew T. <at...@ga...>]

Hi,

I recently discovered that some of my code was passing unicode strings to
orderBy and that this worked as long as the strings didn't start with "-".
When they did start with "-", the _mungeOrderBy check (line 69 in
sresults.py) didn't detect the "-" because the strings were of type unicode
and not type str and _mungeOrderBy checks for str and not basestring.

I was just wondering if this was on purpose or not as it looks like there
are other places in the sqlobject code that do check for type basestring.

Andrew

Re: [SQLObject] Indexes with primary key

[Oleg B. <ph...@ph...>]

On Tue, Aug 26, 2014 at 09:20:25AM +0200, Gert Burger <ger...@gm...> wrote:
> We have some queries which needs to find the oldest/latest rows which match
> certain conditions and having the id field as the last column in an index
> provides us with huge performance gains(Due to significantly less random
> reads of old data).
> 
> Something like: 'SELECT id FROM table WHERE cond1 AND cond2 AND cond3 ORDER
> BY id DESC LIMIT 1;'
> 
> Without the id column( index(col1, col2, col3) ) Postgres needs to fetch
> all the matching rows before it can sort them and return the result. With
> the id column( index(col1, col2, col3, id) ) in the index and as the last
> column in the index it allows Postgres to 'instantly' lookup the first/last
> id for a set of conditions without fetching all the rows and sorting
> them(Since they would already be sorted in the index).

   I see now.

> Do you any suggestions on how I can work around this limitation?

   Either patch SQLObject or create an index at the SQL level; you don't
need to do everything through SQLObject.

> On Tue, Aug 26, 2014 at 12:21 AM, Oleg Broytman <ph...@ph...> wrote:
> > On Mon, Aug 25, 2014 at 10:22:32AM +0200, Gert Burger <
> > ger...@gm...> wrote:
> > > Is it possible to create indexes using SQLO that include the current
> > > 'Table's primary key?
> > > eg DatabaseIndex(col1, col2, col3, 'id')
> > >
> > > Currently SQLO is complaining that the column doesn't exist.
> >
> >    It seems you're right -- SQLObject creates indices that can only
> > include explicitly declared columns, and id is and implicit column.
> >
> >    On the other hand why do you want to create and index with id at all?
> > Isn't an index with a unique non-null column equivalent to index with
> > exactly that column?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Indexes with primary key

[Gert B. <ger...@gm...>]

Hi

We have some queries which needs to find the oldest/latest rows which match
certain conditions and having the id field as the last column in an index
provides us with huge performance gains(Due to significantly less random
reads of old data).

Something like: 'SELECT id FROM table WHERE cond1 AND cond2 AND cond3 ORDER
BY id DESC LIMIT 1;'

Without the id column( index(col1, col2, col3) ) Postgres needs to fetch
all the matching rows before it can sort them and return the result. With
the id column( index(col1, col2, col3, id) ) in the index and as the last
column in the index it allows Postgres to 'instantly' lookup the first/last
id for a set of conditions without fetching all the rows and sorting
them(Since they would already be sorted in the index).

Do you any suggestions on how I can work around this limitation?


On Tue, Aug 26, 2014 at 12:21 AM, Oleg Broytman <ph...@ph...> wrote:

> Hi!
>
> On Mon, Aug 25, 2014 at 10:22:32AM +0200, Gert Burger <
> ger...@gm...> wrote:
> > Is it possible to create indexes using SQLO that include the current
> > 'Table's primary key?
> > eg DatabaseIndex(col1, col2, col3, 'id')
> >
> > Currently SQLO is complaining that the column doesn't exist.
>
>    It seems you're right -- SQLObject creates indices that can only
> include explicitly declared columns, and id is and implicit column.
>
>    On the other hand why do you want to create and index with id at all?
> Isn't an index with a unique non-null column equivalent to index with
> exactly that column?
>
> Oleg.
> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
>
> ------------------------------------------------------------------------------
> Slashdot TV.
> Video for Nerds.  Stuff that matters.
> http://tv.slashdot.org/
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>

Re: [SQLObject] Indexes with primary key

[Oleg B. <ph...@ph...>]

Hi!

On Mon, Aug 25, 2014 at 10:22:32AM +0200, Gert Burger <ger...@gm...> wrote:
> Is it possible to create indexes using SQLO that include the current
> 'Table's primary key?
> eg DatabaseIndex(col1, col2, col3, 'id')
> 
> Currently SQLO is complaining that the column doesn't exist.

   It seems you're right -- SQLObject creates indices that can only
include explicitly declared columns, and id is and implicit column.

   On the other hand why do you want to create and index with id at all?
Isn't an index with a unique non-null column equivalent to index with
exactly that column?

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Indexes with primary key

[Gert B. <ger...@gm...>]

Hi

Is it possible to create indexes using SQLO that include the current
'Table's primary key?
eg DatabaseIndex(col1, col2, col3, 'id')

Currently SQLO is complaining that the column doesn't exist.

Regards
Gert Burger

[SQLObject] SQLObject 2.0.0a1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 2.0.0a1, the first alpha of branch 2.0 of
SQLObject. This is the first release that was developed after switching from
Subversion to git!


What's new in SQLObject
=======================

Features & Interface
--------------------

* DateTimeCol and TimeCol can read and write values with microseconds.

  WARNING: backward compatibility problem! Date/Time columns created
  with microseconds cannot be read back from SQLite databases (and
  perhaps other backends) with versions of SQLObject older than 1.7.

Minor features
--------------

* Upgrade ez_setup to 5.4.1.

Development
-----------

* Development was switched from Subversion to git.

Contributor for this release is Geoffrey Wossum.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/2.0.0a1dev-20140801

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Convert svn to git

[Oleg B. <ph...@ph...>]

Hello! Ready. I created two repositories: "fullhistory" preserves the
entire history from SVN repository, "sqlobject" is the development repo
with those branches that are currently maintained - 1.5, 1.6, 1.7 and
master; those branches preserves their history too; I decided not to cut
history - it's small enough.

   http://sourceforge.net/p/sqlobject/sqlobject
   http://sourceforge.net/p/sqlobject/fullhistory

   https://github.com/sqlobject/sqlobject
   https://github.com/sqlobject/fullhistory

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Converting svn to git

[Oleg B. <ph...@ph...>]

On Mon, Jul 21, 2014 at 11:57:29PM +0200, Oleg Broytman <ph...@ph...> wrote:
>    Along with full history and development repositories at github there
> will be a documentation repository with generated docs. Actually, it's
> already there; docs are visible at http://sqlobject.github.io/ .

   I forgot to mention that I've register an "organization" at github
called, naturally, "sqlobject": https://github.com/sqlobject . Thanks
goodness it was free.

>    Currently I am developing a git workflow (if there will be any).
> Perhaps I preserve the current workflow. With it, master will be the new
> trunk with all the latest unstable code; from it stable branches will be
> branched off. With such workflow it'd be a bit hard to merge pull
> requests directly from github web interface; I think I'll merge them
> locally and then push merges.

   Or may be I should adapt linux-like forkflow. With it, branch 1.5
would become master, stable or oldstable, 1.6 -- master or stable,
1.7 -- next or master, and 2.0 -- next or pu (proposed updates).

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Converting svn to git

[Oleg B. <ph...@ph...>]

Hello, all!

   I've been working for some time behind the scene on converting the
subversion repository to git in hope it helps to revive development a
bit. Now when I'm mostly done I decided to communicate what's going on.

   First, I decided it must be git; git is a clear winner now.

   Second, I want to preserve the entire history, so I decided to
convert entire subversion repository to git. To do that I need a mapping
from svn login names to committers names and email addresses. I
collected them from svn and the mailing list archive. There are exactly
20 committers!
   Today I wrote 18 mail messages (excluding Ian Bicking and me from the
list of committers) asking their permissions to use their names and
emails in the public git repositories. I already get a few errors back;
some mailboxes are no longer available at their original domains; even
worse, some domains are no longer available or don't accept mail.
   One person I have to hunt especially hard -- he used 4 different
email addresses, none of which are now available. Finally I contacted
him via SF.net and he already replied -- the first one of those 18! He
gave me sixths address (-:
   I'm waiting for the other committers. As for unavailable ones -- I'm
afraid I have to use whatever addresses I have for them.

   After the conversion there will be two repositories -- one with full
history and another with a small subset of active branches; currently
these are branches 1.5, 1.6, 1.7 and the trunk^W master.
   I will push these repositories to SF and github; I still value SF as
hosting; with distributed nature of git it's no longer a problem to have
clones/forks/mirrors all over the Net.
   Full history repository will be read-only; the other one is for
development. Repository at SF will be configured to send email
notifications on every push to sqlobject-cvs (heh) mailing list.

   Along with full history and development repositories at github there
will be a documentation repository with generated docs. Actually, it's
already there; docs are visible at http://sqlobject.github.io/ .

   Currently I am developing a git workflow (if there will be any).
Perhaps I preserve the current workflow. With it, master will be the new
trunk with all the latest unstable code; from it stable branches will be
branched off. With such workflow it'd be a bit hard to merge pull
requests directly from github web interface; I think I'll merge them
locally and then push merges.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.7.0b1

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.7.0b1, the first beta of the upcoming
release of branch 1.7 of SQLObject.


What's new in SQLObject
=======================

* Python 2.5 is no longer supported. The minimal supported version is
  Python 2.6.

* DateTimeCol and TimeCol can read values with microseconds (created by
  SQLObject 2.0) but do not write microseconds back.

* Upgrade ez_setup to 5.3.

* Adapt duplicate error message strings for SQLite 3.8.

Contributors for this release are Geoffrey Wossum and Neil Muller.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.7.0b1dev-r4758

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Join with results from both tables

[Oleg B. <ph...@ph...>]

Hi!

On Mon, Jun 16, 2014 at 08:50:44PM +0000, "Goldberg, Arthur P" <art...@ms...> wrote:
> Hi
> 
> I'm just learning sqlobject and find it pretty neat!

   Welcome!

> Suppose I have this:
> from sqlobject import *
> 
> class Variant2(SQLObject):
>     class sqlmeta:
>         style = Style(longID=True)
>     ref = StringCol()
>     alt = StringCol()
>     SubjectID = StringCol()
> 
> class Subject2(SQLObject):
>     FamilyID = StringCol()
>     IndivID = StringCol( alternateID=True, length=50 )  # do not know if this is long enough
>     Sex = StringCol()
> 
> connection = connectionForURI(Minerva_URI)
> connection.debug = True
> sqlhub.processConnection = connection
> Variant2.dropTable( True, )
> Variant2.createTable()
> Subject2.dropTable( True, )
> Subject2.createTable()
> 
> Variant2(
>     ref = 'A',
>     alt = 'C',
>     SubjectID = 'Sub1' )
> 
> Variant2(
>     ref = 'A',
>     alt = 'G',
>     SubjectID = 'Sub2' )
> 
> Subject2( FamilyID = '', IndivID = 'Sub1', Sex = '1' )
> Subject2( FamilyID = '', IndivID = 'Sub2', Sex = '2' )
> 
> for var in Variant2.select(
>     """ subject2.indiv_id = Variant2.SubjectID""",
>     clauseTables=['subject2']):
>     print var
> 
> How would I generate a query that joins Variant2 and subject2? Like this:
> 
> SELECT Variant2.Variant2_id, Variant2.ref, Variant2.alt, Variant2.AAC, Variant2.SubjectID, subject2.Sex FROM subject2, Variant2 WHERE  subject2.indiv_id = Variant2.SubjectID;


for var in Variant2.select(Subject2.q.IndivID==Variant2.q.SubjectID):
    print var

   When you use magic .q. attributes SQLObject derives clauseTables
automatically; it lists all tables used in WHERE clause.

> Also, how could I define SubjectID as a foreign key that references indiv_id?

   Alas, that much harder. Short answer is this (I show only relevant
changes):

class Variant2(SQLObject):
    class sqlmeta:
        idType = str
    Subject = ForeignKey('Subject2', refColumn='IndivID')

   'idType = str' is required because you want SubjectID to be a string
foreign key. But at the same time it changes the type of the 'id' column --
it also becomes TEXT and loses autoincrement property so you have to
assign it manually. The entire programs is now:

class Variant2(SQLObject):
    class sqlmeta:
        idType = str
        style = Style(longID=True)
    ref = StringCol()
    alt = StringCol()
    Subject = ForeignKey('Subject2', refColumn='IndivID')

class Subject2(SQLObject):
    FamilyID = StringCol()
    IndivID = StringCol( alternateID=True, length=50 )  # do not know if this is long enough
    Sex = StringCol()

Variant2.createTable()
Subject2.createTable()

Variant2(
    id = '1',
    ref = 'A',
    alt = 'C',
    SubjectID = 'Sub1' )

Variant2(
    id = '2',
    ref = 'A',
    alt = 'G',
    SubjectID = 'Sub2' )

Subject2( FamilyID = '', IndivID = 'Sub1', Sex = '1' )
Subject2( FamilyID = '', IndivID = 'Sub2', Sex = '2' )

for var in Variant2.select(Subject2.q.IndivID==Variant2.q.SubjectID):
    print var

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] Join with results from both tables

[Goldberg, A. P <art...@ms...>]

Hi

I'm just learning sqlobject and find it pretty neat!

Suppose I have this:
from sqlobject import *

class Variant2(SQLObject):
    class sqlmeta:
        style = Style(longID=True)
    ref = StringCol()
    alt = StringCol()
    SubjectID = StringCol()

class Subject2(SQLObject):
    FamilyID = StringCol()
    IndivID = StringCol( alternateID=True, length=50 )  # do not know if this is long enough
    Sex = StringCol()

connection = connectionForURI(Minerva_URI)
connection.debug = True
sqlhub.processConnection = connection
Variant2.dropTable( True, )
Variant2.createTable()
Subject2.dropTable( True, )
Subject2.createTable()

Variant2(
    ref = 'A',
    alt = 'C',
    SubjectID = 'Sub1' )

Variant2(
    ref = 'A',
    alt = 'G',
    SubjectID = 'Sub2' )

Subject2( FamilyID = '', IndivID = 'Sub1', Sex = '1' )
Subject2( FamilyID = '', IndivID = 'Sub2', Sex = '2' )

for var in Variant2.select(
    """ subject2.indiv_id = Variant2.SubjectID""",
    clauseTables=['subject2']):
    print var

How would I generate a query that joins Variant2 and subject2? Like this:

SELECT Variant2.Variant2_id, Variant2.ref, Variant2.alt, Variant2.AAC, Variant2.SubjectID, subject2.Sex FROM subject2, Variant2 WHERE  subject2.indiv_id = Variant2.SubjectID;

Also, how could I define SubjectID as a foreign key that references indiv_id?

Thanks
Arthur




---

Arthur Goldberg
Associate Professor of Psychiatry
Seaver Autism Center and Icahn Institute for Genomics & Multiscale Biology
Icahn School of Medicine at Mount Sinai
Seaver Center, Room ABE-33
212-241-4229
Art...@ms...<mailto:Art...@ms...>
Follow us on Twitter @IcahnInstitute<https://twitter.com/IcahnInstitute>

[SQLObject] SQLObject 1.6.0

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.6.0, the first stable release of branch
1.6 of SQLObject.


What's new in SQLObject
=======================

Features & Interface
--------------------

* Python 2.4 is no longer supported. The minimal supported version is
  Python 2.5.

* Support for Python 2.5 is declared obsolete and will be removed
  in the next release.

* Upgrade ez_setup to 1.4.2.

* Adapt duplicate error message strings for SQLite 3.8.

Contributor for this release is Neil Muller.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.6.0

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

Re: [SQLObject] Roadmap to 2.0 (up to the last microsecond)

[fetchinson . <fet...@go...>]

On 5/1/14, Oleg Broytman <ph...@ph...> wrote:
> Hello!
>
>    A big part of my frustration was that I created a backward
> incompatible version and didn't know where and how to move further from
> there.
>    Now I see it was stupid. Such a major incompatibility should only be
> introduced in version 2.0. Gradually if possible.
>
>    So my plan currently is:
>
> -- Completely remove support for microseconds from branch 1.6; deprecate
>    support for Python 2.5 (format ".%f" for microseconds is only
>    supported in 2.6+).
> -- Create branch 1.7; drop support for Python 2.5, minimally supported
>    version will be 2.6; restore the code to read microseconds (from
>    databases created with SO 2.0) but not write them.
> -- Create branch 2.0 with full support for microseconds.
>
> PS. I beg your pardon. I said something about microseconds in the
> subject but that was only a pun. I cannot promise months, even less
> concrete dates. I'm sorry.
>
> Oleg.

Sounds great, Oleg!


> --
>      Oleg Broytman            http://phdru.name/            ph...@ph...
>            Programmers don't die, they just GOSUB without RETURN.
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> sqlobject-discuss mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
>


-- 
Psss, psss, put it down! - http://www.cafepress.com/putitdown

Re: [SQLObject] Roadmap to 2.0 (up to the last microsecond)

[<ht...@ma...>]

Plan sounds sensible to me -- thank you for your continued work.

ht
-- 
		    Henry S. Thompson, Markup Systems Ltd.
               Cavers Garden Farm, Denholm; by Hawick; TD9 8LN
                            +44 (0) 7866 471 388
	       Fax: (44) 131 651-1426, e-mail: ht...@ma...
			URL: http://www.markup.co.uk/
[mail really from me _always_ has this .sig -- mail without it is forged spam]

[SQLObject] Roadmap to 2.0 (up to the last microsecond)

[Oleg B. <ph...@ph...>]

Hello!

   A big part of my frustration was that I created a backward
incompatible version and didn't know where and how to move further from
there.
   Now I see it was stupid. Such a major incompatibility should only be
introduced in version 2.0. Gradually if possible.

   So my plan currently is:

-- Completely remove support for microseconds from branch 1.6; deprecate
   support for Python 2.5 (format ".%f" for microseconds is only
   supported in 2.6+).
-- Create branch 1.7; drop support for Python 2.5, minimally supported
   version will be 2.6; restore the code to read microseconds (from
   databases created with SO 2.0) but not write them.
-- Create branch 2.0 with full support for microseconds.

PS. I beg your pardon. I said something about microseconds in the
subject but that was only a pun. I cannot promise months, even less
concrete dates. I'm sorry.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.

[SQLObject] SQLObject 1.5.2

[Oleg B. <ph...@ph...>]

Hello!

I'm pleased to announce version 1.5.2, the second bugfix release of branch
1.5 of SQLObject.


What's new in SQLObject
=======================

* Adapt duplicate error message strings for SQLite 3.8.

Contributor for this release is Neil Muller.

For a more complete list, please see the news:
http://sqlobject.org/News.html


What is SQLObject
=================

SQLObject is an object-relational mapper.  Your database tables are described
as classes, and rows are instances of those classes.  SQLObject is meant to be
easy to use and quick to get started with.

SQLObject supports a number of backends: MySQL, PostgreSQL, SQLite,
Firebird, Sybase, MSSQL and MaxDB (also known as SAPDB).


Where is SQLObject
==================

Site:
http://sqlobject.org

Development:
http://sqlobject.org/devel/

Mailing list:
https://lists.sourceforge.net/mailman/listinfo/sqlobject-discuss

Archives:
http://news.gmane.org/gmane.comp.python.sqlobject

Download:
https://pypi.python.org/pypi/SQLObject/1.5.2

News and changes:
http://sqlobject.org/News.html

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            ph...@ph...
           Programmers don't die, they just GOSUB without RETURN.