The PostgresV3 code in squeak uses subclasses of Compiler and Parser to make sure that PG3SchemaMirror subclasses can parse plsql code. That looks like a nice way to work. What do we need to do to do something similar with the Opal based infrastructure? What subclasses do I need, what methods should I override? Stephan
On 01 Oct 2014, at 14:30, Stephan Eggermont <stephan@stack.nl> wrote:
The PostgresV3 code in squeak uses subclasses of Compiler and Parser to make sure that PG3SchemaMirror subclasses can parse plsql code. That looks like a nice way to work.
What do we need to do to do something similar with the Opal based infrastructure? What subclasses do I need, what methods should I override?
Normally it should be enough to replace all Parser and Compiler reference by Smalltalk compilerClass (as this gives you a Facade that implement still the old APIs of both parser and compiler). Marcus
2014-10-01 9:30 GMT-03:00 Stephan Eggermont <stephan@stack.nl>:
The PostgresV3 code in squeak uses subclasses of Compiler and Parser to make sure that PG3SchemaMirror subclasses can parse plsql code. That looks like a nice way to work.
Are you using/planning to use PostgresV3? What are its advantages over current driver (PostgresV2)? Regards, Esteban A. Maringolo
participants (3)
-
Esteban A. Maringolo -
Marcus Denker -
Stephan Eggermont