Re: providing tokenized version of parsed SQL script

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 28/04/2010 02:20, Robert Haas wrote:
> On Tue, Apr 27, 2010 at 7:45 PM, Jehan-Guillaume (ioguix) de Rorthais
> <ioguix(at)free(dot)fr> wrote:
>> I thought Michael was trying to write a tokenizer based on node tree
>> returned by raw_parser. As it seems Michael is not even sure about what
>> he's trying to do, I prefer refocus a bit this thread
> [...]
>> Having dropped an eye here and there in the parser code, I am not sure
>> where I could get required info and mix them to produce something close
>> to my draft yet.
>> But I prefer to discussing first before spending too much time and
>> throwing any potential code after...
>
> I can't quite tell, from reading this, what you're trying to do with this...

I would like to do what I described here:

http://archives.postgresql.org/pgsql-hackers/2010-04/msg00974.php

Pavel Stehule convinced me a function would be a better approach than a
new SQL keyword. Moreover he points an existing function in the Oracle
ecosystem that is doing very closely what I descibed in my draft:

http://archives.postgresql.org/pgsql-hackers/2010-04/msg00976.php
http://www.pgsql.cz/index.php/Oracle_functionality_%28en%29#PLVlex

Presently I am just studying some parts of the parser code to find where
I could find :
- token/lexer representation of a SQL script
- type of each token

Sorry the mess and confusion, hope this mail is clearer ?

>
> ...Robert

- --
JGuillaume (ioguix) de Rorthais
http://www.dalibo.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkvX7aIACgkQxWGfaAgowiI5PQCeITOqAlCbeFyYc2KdHPUOfXhe
YY8An0jdfF31SK75bmd21ixFffXiyoEF
=ymbW
-----END PGP SIGNATURE-----