Postgres Pro
Downloads
Home   >   mailing lists

Thread: Using double quotes in create table statement!

Using double quotes in create table statement!

From
"Israel Calderon"
Date:
Hello I am currently analyzing a db schema and ran across something which I
am not familiar with. The table name within the create statement is enclosed
within double quotes as well as a column within the table. Heres the format:

CREATE TABLE "xyz"(
act_act character varying (40),
"action" character varying (30),
st_id uniqueidentifier DEFAULT newid() NOT NULL
);


The "xyz" and "action" portions of this create statement I do not
understand. Can anyone elaborate on this? Much appreciated!





_________________________________________________________________
The new MSN 8: smart spam protection and 2 months FREE*
http://join.msn.com/?page=features/junkmail

Re: Using double quotes in create table statement!

From
Bruno Wolff III
Date:
On Tue, May 06, 2003 at 12:38:59 -0400,
  Israel Calderon <icalderus@hotmail.com> wrote:
>
> Hello I am currently analyzing a db schema and ran across something which I
> am not familiar with. The table name within the create statement is
> enclosed within double quotes as well as a column within the table. Heres
> the format:
>
> CREATE TABLE "xyz"(
> act_act character varying (40),
> "action" character varying (30),
> st_id uniqueidentifier DEFAULT newid() NOT NULL
> );
>
>
> The "xyz" and "action" portions of this create statement I do not
> understand. Can anyone elaborate on this? Much appreciated!

Quotes allow you to preserve case in the name, use some special charcters
that you couldn't use without quoting or use reserved words for the names.

Select, but returning binary data.

From
"M. Bastin"
Date:
Hi all,

I can't figure out how to issue a select statement that will return
binary data instead of textual data.  (pgSQL backend message "B"
instead of "D".)

I'm also having some trouble finding documentation about "function
calls", and what their use is.  Is their anyone out there using that
animal, or is everyone happily using functions in regular queries?
If someone could direct me to some sample function call statements,
and their result...

Thanks,

Marc

Re: Select, but returning binary data.

From
Tom Lane
Date:
"M. Bastin" <marcbastin@mindspring.com> writes:
> I can't figure out how to issue a select statement that will return
> binary data instead of textual data.  (pgSQL backend message "B"
> instead of "D".)

You can't; the only operation that produces B messages is a FETCH
from a binary cursor.

This will be improved on in 7.4, btw.

> I'm also having some trouble finding documentation about "function
> calls", and what their use is.

Very little --- I'd call the feature obsolete myself.  You might
as well just do "SELECT foo(...)".

            regards, tom lane

Storing ole object in postgresql

From
"Juliet May"
Date:
I need to access a bitmap that is stored in an ole object that was imported
into the database as a blob into a column of type lo. I am able to move the
ole object in and out of the database and I am able to view the bitmap in
the ole object in the original application it was created in. But, I need to
display the bitmap image on a web page.

Any ideas of how to extract the bitmap image from the ole object which is
stored as a blob in the database?

TIA for any help you can provide.

Julie