> Pavel, > if it was a simple plain dynami statement, I could create it by string > concatenation, literal_ and ident_ quoting and so on.
the situation isn't too simply like you see it. PostgreSQL supports composite and nested types. For this types you cannot use quote* functions. Next problem is NULL values. I did this work four years ago and http://archives.postgresql.org/pgsql-patches/2006-08/msg00271.php it was rejected - from good reasons. You can see more messages from this time in archive. In plpgsql we don't would to supply SQL parser - so when you would to identify pleaseholders, then your implementation will be slow or buggy. Regards Pavel Stehule > But this is not my case. > I'm exploring an alternative approach to the table partitioning > (http://notsononsense.blogspot.com/2009/12/postgresql-different-approach-to-table.html). > And being able to handle dynamic DML and DDL is a key point, also for > the traditional one. > In practice, the whole EXECUTE...USING command is generated > dynamically, so not even the names or the values passed after the > USING lexem are known at that time. > > -- > Vincenzo Romano > NotOrAnd Information Technologies > cel. +39 339 8083886 | gtalk. vincenzo.rom...@notorand.it > fix. +39 0823 454163 | skype. notorand.it > fax. +39 02 700506964 | msn. notorand.it > NON QVIETIS MARIBVS NAVTA PERITVS > -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
