Oleg Broytmann wrote:
> On Wed, Jul 25, 2007 at 08:22:34AM -0700, Fred C wrote:
>> I use PostgreSQL 8 and everything works fine with SQLObject. For the
>> quotes PostgreSQL support both syntaxes.
>
>8.2? 8.3?
Works with 8.2.4 to me.
-
On 7/25/07, Luke Opperman <[EMAIL PROTECTED]> wrote:
> It's missing something, presumably you want to return the traversed FKs (or
> their .q expression) in addition to the classes found in the search (building
> the expressions as X.id == Y.id will not get the results intended, you want
> X.fkToYI
It's missing something, presumably you want to return the traversed FKs (or
their .q expression) in addition to the classes found in the search (building
the expressions as X.id == Y.id will not get the results intended, you want
X.fkToYID == Y.id). I'd probably let .q handle more of the work in
Bu
Oleg Broytmann wrote:
On Tue, Jul 24, 2007 at 09:35:34AM -0700, Tim Black wrote:
Project.get(1).addContractor(Person.get(1))
Traceback (most recent call last):
File "", line 1, in ?
AttributeError: 'Project' object has no attribute 'addContractor'
What is the right way to specif
Right now I am using 8.2 on FreeBSD.
postgresql-client-8.2.4 PostgreSQL database (client)
postgresql-server-8.2.4_1 The most advanced open-source database
available anywhere
-fred-
On Jul 25, 2007, at 8:29 AM, Oleg Broytmann wrote:
> On Wed, Jul 25, 2007 at 08:22:34AM -0700, Fred C wrote:
>>
Why not change SQLObject to used '' instead of \' since it is the SQL
standard way to write a single quote. The other databases seems to
support this syntax.
fred[601]> sqlite3
SQLite version 3.3.4
Enter ".help" for instructions
sqlite> create table foo (bar char(32));
sqlite> insert into foo
On Wed, Jul 25, 2007 at 09:13:22AM -0700, Fred C wrote:
> Why not change SQLObject to used '' instead of \' since it is the SQL
> standard way to write a single quote.
This is exactly what I want to do. I thought PostgreSQL before 8.0
didn't support '' style quoting but I was wrong, even Pg 7.3
On Wed, Jul 25, 2007 at 08:34:37AM -0700, Fred C wrote:
> Right now I am using 8.2 on FreeBSD.
There is a bug report at the SF tracker:
https://sourceforge.net/tracker/index.php?func=detail&aid=1759920&group_id=74338&atid=540672
about Pg 8.2.3 on Darwin. It seems Pg 8.2 on Darwin forbid \' s
Some of the orderBy operations I need to perform occur with joins
between lots of tables. Instead of having to hand write all the
expressions prescribed by this post:
http://osdir.com/ml/python.sqlobject/2005-06/msg00055.html.
I instead wrote a BreadthFirstSearch algorithm to scan through my
SQLOb
On Wed, Jul 25, 2007 at 08:22:34AM -0700, Fred C wrote:
> I use PostgreSQL 8 and everything works fine with SQLObject. For the
> quotes PostgreSQL support both syntaxes.
8.2? 8.3?
> This is from the reference manual.
>
> 4.1.2.1. String Constants
"A string constant in SQL is an arbitrary s
I use PostgreSQL 8 and everything works fine with SQLObject. For the
quotes PostgreSQL support both syntaxes.
This is from the reference manual.
4.1.2.1. String Constants
A string constant in SQL is an arbitrary sequence of characters
bounded by single quotes (’), for example ’This is a str
Hello.
Are here Postgres users who haven't switched to PostgreSQL 8.+? The
problem is that Postgres 8+ changed quoting style from \' to '', and it's
impossible for SQLObject to support both styles simultaneously, so if
everyone has upgraded I will change quoting style in the trunk to ''.
Oleg.
On Tue, Jul 24, 2007 at 09:35:34AM -0700, Tim Black wrote:
> >>> Project.get(1).addContractor(Person.get(1))
> Traceback (most recent call last):
> File "", line 1, in ?
> AttributeError: 'Project' object has no attribute 'addContractor'
>
> What is the right way to specify that I'm adding a cont
13 matches
Mail list logo
