Madison Kelly wrote:
Is there a way to store the name in raw binary?
Yes: bytea.
-O
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
rumor has it that Richard wrote:
> Franco Bruno Borghesi wrote:
> > You could write a trigger like this:
> >
> >
> > CREATE OR REPLACE FUNCTION checkDate() RETURNS TRIGGER LANGUAGE
> > 'plpgsql' AS ' DECLARE
> > limitDate DATE DEFAULT current_date-''1 year''::INTERVAL;
> > BEGIN
> > IF (
I am interested in seting up postgres 7.4 or 8.0
which is best on SuSe 8.0 professional and where
should
I put the tar.gz for unzip and install?
Thank you.
Yahoo! Mail
Stay connected, organized, and protected. Take the tour:
http://tour.mail.yahoo.com/mailtour.html
---
On Mon, May 09, 2005 at 02:05:14AM +1000, Brendan Jurd wrote:
> CREATE TABLE foo (
> foo int NOT NULL REFERENCES bar INDEX
> );
>
> ... would be marvellous
I agree that it would be handy. Another possibility is throwing a NOTICE
or even WARNING if you create a foreign key that isn't covered by a
Michael Ben-Nes <[EMAIL PROTECTED]> writes:
> You can set postgresql.conf to log all queries to a file.
> Sadly you cant distinguish between the databases.
See log_line_prefix in 8.0.
regards, tom lane
---(end of broadcast)-
Does anybody else think it would be cool if you could use a shorthand
expression for creating an index on a foreign key? I think it's fair
to say that in the majority of cases, if you're using a foreign key,
you're going to want an index on it.
I know that it was decided a fair few releases ago t
You can set postgresql.conf to log all queries to a file.
Sadly you cant distinguish between the databases.
Hrishikesh Deshmukh wrote:
Hi All,
Does Postgresql have a "sql history of queries run" capability?
Any ideas/pointers will be a great help. Could one capture the order
and SQL queries run?!
T
> There is a table t1(member_id integer primary key, member_name text,
> address text, phone text, email text). I have to reach each member by
> either adress, phone or email. Unfortunately some of address field
> have wrong encoded data. In this case I will use phone or email to
> reach them.
>
> Is there a way to store the name in raw binary? If so, would this not
> be safe because to postgresql it should no longer matter what data is or
> represents, right? Maybe there is a third option I am not yet concidering?
In the backup rename the file and add another file
.README
which expla
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 3:31 PM
> To: John Hansen
> Cc: [EMAIL PROTECTED]; pgsql-general@postgresql.org;
> pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> > Tatsuo Ishii wrote:
> > > Sent: Sunday, May 08, 2005 12:01 PM
>
Am Sonntag, den 08.05.2005, 14:30 +0900 schrieb Tatsuo Ishii:
...
> Actually I myself thought as you are before. Later I found that it was
> not so good idea. People already have invalid encoded data in their
> precious database and have very hard time to migrate to newer version
> of PostgreSQL be
11 matches
Mail list logo
