t would be handy
to be able to generate these without having to load in special
extensions. It's not the biggest deal though since we can run
initialization code to get the database set up... just more effort.
Patrick Earl
On Mon, Jul 11, 2011 at 11:19 AM, Joshua D. Drake
wrote:
for your consideration in this matter.
Patrick Earl
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
lected rows.
select * from pet left join cat ... for update of pet, cat;
On a conceptual level, I still tend to think of select for update as
"locking the data returned by the query." If no data is returned by
the query, I don't get a lock on that non-data. Is this an area
On Sun, May 1, 2011 at 4:05 PM, Tom Lane wrote:
> Patrick Earl writes:
>> The query to get all the pets is as follows:
>
>> select * from Pet
>> left join Dog on Dog.Id = Pet.Id
>> left join Cat on Cat.Id = Pet.Id
>
>> Now suppose you want to lock
char" which defaults to zero doesn't work on PostgreSQL because it's
apparently still using zero-terminated string functions. :(
Aside from those two things, it looks like PostgreSQL is going to be
passing all the tests soon, so that's good news. :)
Patrick Earl
--
Se
