-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for all the replies everyone. Not really knowing what a cursor
is, I suppose I have some work to do. I can do the SELECT/LIMIT/
OFFSET approach but that seems like kind of a headache, esp. when its
hard to predict what # of rows will max
around.
comments?
On Mar 12, 2007, at 12:49 PM, A.M. wrote:
On Mar 12, 2007, at 15:33 , Neal Clark wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for all the replies everyone. Not really knowing what a
cursor is, I suppose I have some work to do. I can do the SELECT/
LIMIT
memory? And if it handles it similar to mysql, does it also
cause the same table locking behaviour?
Thanks,
Neal Clark
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (Darwin)
iD8DBQFF9OiIOUuHw4wCzDMRAma+AJ4pUPjVmPZUn7GYlVe4diTQaMCShwCghqCb
7hKG4ZbrSzhO2aqqyIyQu8k=
=OkYX
-END PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi All.
I was wondering...I currently have indexes on the primary key id and
foreign key id's for tables that resemble the following. Is this a
good idea/when would it benefit me? I don't want waste a lot of
unnecessary space on indexes.
Have you tried the CREATE USER command from psql/a client
application? I.e. to create a user that is not a super user and can't
create databases or roles:
CREATE USER [name] WITH NOCREATEDB NOCREATEUSER PASSWORD '[password]';
as for your 'createuser' problem... i've got nothin
On
