Hi John,
Thanks for the response
I need this because it is a customer requirement. The underlying tables
the api will query are dynamically created, they are period/content
partitioned and distributed across multiple servers and database types...
not just postgres. The api/function will
On 8/13/2014 10:59 PM, Andrew Bartley wrote:
I need this because it is a customer requirement. The underlying
tables the api will query are dynamically created, they are
period/content partitioned and distributed across multiple servers and
database types... not just postgres. The
On 14 Aug 2014, at 7:59, Andrew Bartley ambart...@gmail.com wrote:
I need this because it is a customer requirement. The underlying tables the
api will query are dynamically created, they are period/content partitioned
and distributed across multiple servers and database types... not just
On Thu, Aug 14, 2014 at 1:17 AM, John R Pierce pie...@hogranch.com wrote:
On 8/13/2014 10:59 PM, Andrew Bartley wrote:
I need this because it is a customer requirement. The underlying tables the
api will query are dynamically created, they are period/content partitioned
and distributed
Hi all,
Is it possible to create a view or foreign table that will do something
like this
select * from table_x
where x_id = 10;
passing the where x_id = 10 to a function
sorta like this
select * from api_function('x = 10')
or
select * from api_function(10)
passing the result set back to
On 8/13/2014 10:08 PM, Andrew Bartley wrote:
Is it possible to create a view or foreign table that will do
something like this
select * from table_x
where x_id = 10;
passing the where x_id = 10 to a function
sorta like this
select * from api_function('x = 10')
or
select * from
