--- Collin Peters <[EMAIL PROTECTED]> wrote:
> The exact problem is that you can't use nextval() with an INSERTable VIEW
I apoligize if I am not understanding your problem correctly. I am unsure as
to intent behind
using nextval() as opposed to currval().
I do not know if the following DDL wi
The exact problem is that you can't use nextval() with an INSERTable VIEW
Problem is the same as that in this post:
http://archives.postgresql.org/pgsql-sql/2003-07/msg00333.php
On 5/3/07, Richard Broersma Jr <[EMAIL PROTECTED]> wrote:
--- Collin Peters <[EMAIL PROTECTED]> wrote:
> I am havin
--- Collin Peters <[EMAIL PROTECTED]> wrote:
> I am having the same problem that is documented elsewhere in the
> archives. Namely when you have a INSERT RULE on a VIEW the nextval()
> function doesn't behave properly (or it doesn't behave how I'd like it
> to).
>
> http://archives.postgresql.o
I am having the same problem that is documented elsewhere in the
archives. Namely when you have a INSERT RULE on a VIEW the nextval()
function doesn't behave properly (or it doesn't behave how I'd like it
to).
http://archives.postgresql.org/pgsql-sql/2003-07/msg00333.php
I'm wondering if anythi
Well, actually it was there last week too :)
>>> "Aaron Bono" <[EMAIL PROTECTED]> 2007-05-03 16:14 >>>
On 5/3/07, Rodrigo De León <[EMAIL PROTECTED]> wrote:
See:
http://archives.postgresql.org/pgsql-general/2005-12/msg00080.php
Man, where was this last week when I needed it. I will have
On 5/3/07, Rodrigo De León <[EMAIL PROTECTED]> wrote:
See:
http://archives.postgresql.org/pgsql-general/2005-12/msg00080.php
Man, where was this last week when I needed it. I will have to keep this
for future reference.
Thanks!
--
===
On 5/2/07, Penchalaiah P. <[EMAIL PROTECTED]> wrote:
I need a user defined function for the following purpose….
If I pass a string with comma ( , ) separated chars/values…. It should be
appear in next line…
Ex: select get_sep_str ('SK, rp, h, j, 6, 9, kl') from dual;
Output :
SK
rp
h
j
6
