; # 2. just split on the dot, assume anonymized name
> return compiled.split(".")[0]
>
> a test suite is included in the attached along with a crazy table name
> test.
>
>
>
> On Wed, Apr 15, 2020, at 10:33 AM, Adrien Berchet wrote:
>
>
> Yes, the fi
func.ST_AsGeoJSON(Lake, 'geom')])
>
> ?
>
> that is, users definitely need this goofy "Table" syntax, right?
>
>
>
> On Wed, Apr 15, 2020, at 7:15 AM, Adrien Berchet wrote:
>
> Ok, thank you for your advice, following it I tried the following (in
> g
gt; OK so use the "t" form with the "geom" name sent as a string, it wants the
> whole row so this is a special Postgresql syntax.There are many ways to
> make it output this and it depends on the specifics of how this is being
> rendered. it may require
it's not going to be any easier to get SQLAlchemy to
> render "t" than it is "t.*". it wants to name columns.
>
>
>
> On Tue, Apr 14, 2020, at 9:45 AM, Adrien Berchet wrote:
>
> I just found that in fact it is possible to just pass the table name to
>
:23, Mike Bayer a
écrit :
> and you can't say "SELECT t.d, t.geom" ? There really should be no
> difference between "t.*" and "t.id, t.geom".
>
>
>
> On Tue, Apr 14, 2020, at 5:31 AM, Adrien Berchet wrote:
>
> The "column names" issue
, ...
And I can't find any way to pass the names to the ROW() constructor:
https://www.postgresql.org/docs/current/sql-expressions.html#SQL-SYNTAX-ROW-CONSTRUCTORS
Le mardi 14 avril 2020 00:47:28 UTC+2, Mike Bayer a écrit :
>
>
>
> On Mon, Apr 13, 2020, at 6:25 PM, Adrien Berchet wrot
Hello there
I tried to integrate your POC in GeoAlchemy2 in the following PR:
https://github.com/geoalchemy/geoalchemy2/pull/258
It is almost working but the ST_AsGeoJSON() function needs a record, not a
list of columns. So the query should be like:
> SELECT ST_AsGeoJSON(t.*)
> FROM t;
>
>
