Re: [SQL] Characters that needs escape characters when inserting to database

On Jan 18, 2006, at 7:21 , Christian Paul B. Cosinas wrote: Can anyone give me a list of characters that needs to be preceded by an escape character before inserting to database. Take a look at this documentation on string constants. It should answer the questions you have. http://www.pos

[SQL] Characters that needs escape characters when inserting to database

Hi, Can anyone give me a list of characters that needs to be preceded by an escape character before inserting to database. Aside from characters listed below what are the other characters? "\" "'" Thanks I choose Polesoft Lockspam to fight spam, and you? http://www.polesoft.com/refer.html

Re: [SQL] Executing plpgsql scripts using psql, is that possible?

> If you want to use plpgsql it will need to be within a function. In your > reply > you mention creating user-defined functions as part of the set up > procedure. > It would not be weird to include the static data function as part of that > procedure and then call it to load the data. I see no re

Re: [SQL] Executing plpgsql scripts using psql, is that possible?

Daniel, On Jan 16, 2006, at 8:55 PM, Daniel CAUNE wrote: Yes, but that requires creating a function while I would prefer not having do so, as I said in my previous mail: "I mean, without creating a function that wraps the whole, of course! :-)". Why? Actually this is not a function; this

Re: [SQL] Executing plpgsql scripts using psql, is that possible?

On Monday 16 January 2006 05:55 pm, Daniel CAUNE wrote: > > -Message d'origine- > > De : [EMAIL PROTECTED] [mailto:pgsql-sql- > > [EMAIL PROTECTED] De la part de John DeSoi > > Envoyé : lundi 16 janvier 2006 08:51 > > À : Daniel CAUNE > > Cc : pgsql-sql@postgresql.org > > Objet : Re: [SQL]

Re: [SQL] Executing plpgsql scripts using psql, is that possible?

> -Message d'origine- > De : [EMAIL PROTECTED] [mailto:pgsql-sql- > [EMAIL PROTECTED] De la part de John DeSoi > Envoyé : lundi 16 janvier 2006 08:51 > À : Daniel CAUNE > Cc : pgsql-sql@postgresql.org > Objet : Re: [SQL] Executing plpgsql scripts using psql, is that possible? > > > On J

Re: [SQL] For update

Hello,   Oh, I got it. Now in 8.0.6   When the view has UNION ALL, then PostgreSQL reports this: SELECT FOR UPDATE is not allowed in subqueries .   I see why:   select * from for update;   After extraction:   select * from UNION ALL for update;   In this case it seems as if "for update" is in su

Re: [SQL] For update

Hello,   Sorry, I have just tried it, and works with 8.0.5. I had missed something then. :(  I like PostgreSQL. :)   Thanks, Otto  2006/1/16, Alvaro Herrera <[EMAIL PROTECTED]>: Ottó Havasvölgyi wrote:> Hello,>> Huh, it was weeks ago, and I thought it was normal. It was a simple view > with one or

Re: [SQL] For update

Ottó Havasvölgyi wrote: > Hello, > > Huh, it was weeks ago, and I thought it was normal. It was a simple view > with one or two inner joins and without aggragates. Perhaps somebody could > try it. I got an error message, that said I cannot do that. I cannot > remember the exact message unfortunate

Re: [SQL] For update

Hello,   Huh, it was weeks ago, and I thought it was normal. It was a simple view with one or two inner joins and without aggragates. Perhaps somebody could try it. I got an error message, that said I cannot do that. I cannot remember the exact message unfortunately.   Best Regards, Otto   2006/1/

Re: [SQL] best way for constants in the database

chester c young wrote: > anybody have a good way to impliment constants in the database? > > using an immutable pgpgsql function, constant_name() - works, but not > necessarily very efficient. A function declared IMMUTABLE should be efficient enough; it'll usually be evaluated once per query at

[SQL] best way for constants in the database

anybody have a good way to impliment constants in the database? using an immutable pgpgsql function, constant_name() - works, but not necessarily very efficient. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http

Re: [SQL] For update

On Mon, Jan 16, 2006 at 02:05:15PM -0300, Alvaro Herrera wrote: > Ottó Havasvölgyi wrote: > > What does this do exactly: > > > > select * from where for update; > > > > Will be locked all the tuples in all tables it retrieves? > > Yes. > > > In 8.0.5 this did not work for me. > > How did it

Re: [SQL] For update

Ottó Havasvölgyi wrote: > What does this do exactly: > > select * from where for update; > > Will be locked all the tuples in all tables it retrieves? Yes. > In 8.0.5 this did not work for me. How did it not work? Was any error message emitted? What is the view definition? -- Alvaro He

Re: [SQL] psql client: technique for applying default values to :variables?

Jeff Boes writes: > Michael Glaesemann wrote: >> You could write a wrapper script that would accept a command line >> argument and load the file with the appropriate SET statement prepended. > > Which really gains me nothing over just: > > $ psql -f myscript.sql -v "MYVAR=${myvar:-default}" > > Th

[SQL] For update

Hello,   What does this do exactly:   select * from where   for update;   Will be locked all the tuples in all tables it retrieves?   In 8.0.5 this did not work for me.   Thanks, Otto

Re: [SQL] psql client: technique for applying default values to :variables?

Michael Glaesemann wrote: > > On Jan 14, 2006, at 23:54 , Jeff Boes wrote: > >> Tony Wasson wrote: > >> >> Sure, but that was not my question. I want to be able to set the >> variable on the command line, BUT have it default to a value inside >> the SQL script if not present on the command line. >

Re: [SQL] Executing plpgsql scripts using psql, is that possible?

On Jan 16, 2006, at 5:35 AM, Daniel CAUNE wrote: I would like to write some administration plpgsql scripts that populate some tables (dimension tables) and to execute them using psql. I’m not sure that is possible with psql as it is with Oracle sqlplus or SQL Server MSQuery: If you wan