On Fri, Feb 6, 2009 at 7:50 PM, Devan Goodwin <[email protected]> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Fri, 6 Feb 2009 19:37:28 +0530 > Gurjeet Singh <[email protected]> wrote: > > > > > > > Hmm.. Although that is doable, I haven't thought about that. The way > > I saw it was that we'd have a IF(ORACLE) CONNECT BY ELSE IF(POSTGRES) > > CALL FUNCTION END kinda code... > > > > Thinking a bit, I don't see a point in porting this to Oracle! The > > calling syntax will be different for both the databases anyway: > > Oracle: > > select x,y from TABLE( function() ); > > Postres: > > select x, y from function() as f( x int, y int). > > > > So I guess we will _have_ to keep two versions of the query at least > > in the python code. The other usage in PL/SQL package is anyway going > > to be ported over. > > > > Best regards, > > Ok this is something we'll need to be very careful with. We kinda knew > this was coming (having to fork queries for each database) but we'll > need to plan ahead for this on our end. The python queries are all just > variables in the source so it's probably in our best interest to setup > a quick framework for using one set of queries by default, and allowing > them to be overridden depending on your database backend. I will add > this to my TODO list. > > However if anything occurs to you for a way we can keep the query > static for both databases that would be great! [?] We can create a view on both DBs with different definitions and get away with it.. ;) -- gurjeet[[email protected] EnterpriseDB http://www.enterprisedb.com singh.gurj...@{ gmail | hotmail | indiatimes | yahoo }.com
<<B56.gif>>
_______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
