Michael Fuhr wrote:
You refer to shs.city. in the select list, but in the from
clause you've aliased shs.city to city. As the SELECT documentation
says,
When an alias is provided, it completely hides the actual name
of the table or function; for example given FROM foo AS f, the
remainder
Hi,
I'm experiencing some weird results with SELECT queries when I recently
switched to using schemas. Basically, the same query works OK when I set
my search_path to include the schema, but it doesn't when I qualify the
tables in my query.
One query that demonstrates the behaviour is (apolo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm having some trouble with transaction isolation levels, and would
appreciate some input on this.
According to the documentation of PostgreSQL 8.0.3, section 12.2:
"Read Committed is the default isolation level in PostgreSQL. When a
transact
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Fuhr wrote:
>What words in section 12.2.1 are you referring to? I see the
>following (emphasis mine):
>
> In effect, a SELECT query sees a snapshot of the database as of
> the instant that that *query* begins to run. Notice that two
> suc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm having some trouble with transaction isolation levels, and would
appreciate some input on this.
According to the documentation of PostgreSQL 8.0.3, section 12.2:
"Read Committed is the default isolation level in PostgreSQL. When a
transactio
