Could you please publicize the regression tests, so it can be used as a status on the project. I would use this to decide whether to get involved or not. I know that a lot of tests will fail, but then I can judge the severity of those fails afterwards and get an actual overview over the project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Perhaps we should just start with running pg_regress and see where we stand. I sure we can chuck out a large number of the test that we don't support like the ones handling plpgsql. Once we have a clear picture on where we stand in regards to the pg tests we can expand them to be more GridSQL specific.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That sounds like a great idea! It should be quite easy to modify the plpgsql queries to run successfully, though, by just creating the methods directly on the underlying nodes and let GridSQL pass the method names on to the underlying nodes without causing an error, so maybe we should just keep the plpgsql tests there?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I will continue the thread from http://forums.enterprisedb.com/posts/list/2627.page;jsessionid=01CB591114486FBA683A09ADD9474022 here as the login on that forum is broken.
Could you please publicize the regression tests, so it can be used as a status on the project. I would use this to decide whether to get involved or not. I know that a lot of tests will fail, but then I can judge the severity of those fails afterwards and get an actual overview over the project.
Perhaps we should just start with running pg_regress and see where we stand. I sure we can chuck out a large number of the test that we don't support like the ones handling plpgsql. Once we have a clear picture on where we stand in regards to the pg tests we can expand them to be more GridSQL specific.
That sounds like a great idea! It should be quite easy to modify the plpgsql queries to run successfully, though, by just creating the methods directly on the underlying nodes and let GridSQL pass the method names on to the underlying nodes without causing an error, so maybe we should just keep the plpgsql tests there?