I'm looking for software that can generate PHP scripts from PostgreSQL
database that will allow for distant users to edit the data.
The idea is to let selected users have EASY access to edit the data
they see, I can't possibly give raw access with pgMyAdmin or anything
of sorts, as it is hardly
could phppgadmin serve your purpose?
http://phppgadmin.sourceforge.net/
---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
wayne schlemitz [EMAIL PROTECTED] writes:
What can I do to finish the last 2 lines and call up
the potgres or pgsql?
We can't help you from such a handwavy description. Show us *exactly*
what you typed and *exactly* what messages you got (cut-and-paste from
your terminal window is good), and
[EMAIL PROTECTED] (Tom Lane) writes:
elein [EMAIL PROTECTED] writes:
What is the current wisdom on setting the fsm variables
for 8.0? How is it different from 7.4? Or is it?
Same as before.
I am assuming these are the values that changed with Jan's changes.
If not what were those
If I understand your description of the problem sufficiently, I believe
you're
running into trouble at the su postres step.
Although I'm quite new to postgres, I do know that creating a user
account
named postgres is recommended, if not required, by the installation
process.
Entering su
Dear Wayne,
Hum! you are not following exactly the instructions for a Short Installation
which is:
./configure
gmake
su
gmake install
adduser postgres
mkdir /usr/local/pgsql/data
chown postgres /usr/local/pgsql/data
su - postgres
/usr/local/pgsql/bin/initdb -D /usr/local/pgsql/data
Hello,
If I have a rule like this:
CREATE OR REPLACE RULE sometable_update AS ON UPDATE TO table2 DO UPDATE
cache SET updated_dt=NULL WHERE tablename='sometable';
CREATE OR REPLACE RULE sometable_insert AS ON INSERT TO table2 DO UPDATE
cache SET updated_dt=NULL WHERE tablename='sometable';
I have built slony 1.0.2 with postgres 7.4.5. This needs to be deployed
on a system other than the one on which is was built. Somebody on our
team had earlier gotten around the problem of not being able to move a
postgres install by manually updating the pg_catalog.pg_proc table. But
it seems like
