On 08/25/2016 11:26 AM, rla...@fastly.com wrote:
Hello all,
I overrided that method as you suggested, and included placeholders for
the other ones being overloaded by calchipan. The reflection functions
now work, and I decided to use the same mechanism as calchipan for DDL
compilation
Hello all,
I overrided that method as you suggested, and included placeholders for the
other ones being overloaded by calchipan. The reflection functions now
work, and I decided to use the same mechanism as calchipan for DDL
compilation (instantiating a Resolver object that is then passed to
Thanks! Will do.
All the best
Raul
On Friday, August 19, 2016 at 3:14:00 PM UTC+1, Mike Bayer wrote:
>
>
>
> On 08/19/2016 06:37 AM, rla...@fastly.com wrote:
> > Hello all,
> >
> > I have implemented the first stab at a PEP 249 adaptor layer for
> > BigQuery and it seems to work well. It is
On 08/19/2016 06:37 AM, rla...@fastly.com wrote:
Hello all,
I have implemented the first stab at a PEP 249 adaptor layer for
BigQuery and it seems to work well. It is possible to create an
engine/connection/cursor, submit an SQL query and get results back (only
SELECT statements for now, API
Hello all,
I have implemented the first stab at a PEP 249 adaptor layer for BigQuery
and it seems to work well. It is possible to create an
engine/connection/cursor, submit an SQL query and get results back (only
SELECT statements for now, API commands will come later). I have moved on
to
On 08/15/2016 09:01 AM, rla...@fastly.com wrote:
I would be interested in contributing towards implementing a dialect for
BigQuery. Is there a minimal dialect implementation that I could use as
a guide on how to start doing this for BigQuery?
I took a peek at BigQuery and the first
I would be interested in contributing towards implementing a dialect for
BigQuery. Is there a minimal dialect implementation that I could use as a
guide on how to start doing this for BigQuery?
Thanks
Raul
--
You received this message because you are subscribed to the Google Groups
