Perhaps you could write a little external that could talk to the backend
directly (although there isn't really much you
can't do from within psql). There is a "driver" for just about any
language you can think of in postgres. In fact, if you
look at the .tcl driver code (my personal favorite),
Len Morgan wrote:
Can I ask why you are using psql instead of the rev functions (which
don't pad)?
Rev Database Functions: You Wish! We Wish!
This is the 2.6.1 engine running on a linux web server...
so, it is relatively "crippled" dBase wise.
all the power tools we would love to be able to
u
Can I ask why you are using psql instead of the rev functions (which
don't pad)?
len morgan
Sadhunathan Nadesan wrote:
Swami
It appears that the -A option to psql does what you want. It's right
at the beginning of the man entry for psql.
To see this in action log in to vel and cd to /tmp,
Swami
It appears that the -A option to psql does what you want. It's right
at the beginning of the man entry for psql.
To see this in action log in to vel and cd to /tmp, then run
psql htde -f event.sql
It looks like this
user_id | event_code | event_time | description