BAh doesn't look like theres anything online to do it...
Derek J. Lambert
@djlambert
:) if I remeber correctly I think the postgres error messages gave some hint where the issue was
a simple CLI validator script wouldn't be a bad idea
Jon West
@ddproxy
Yeah and to compare with postgres error if applicable... anyways moment
Jon West
@ddproxy
ERROR: Invalid endian flag value encountered.
********** Error **********
ERROR: Invalid endian flag value encountered.
SQL state: XX000
Derek J. Lambert
@djlambert
that's interesting
wkb-parser should have thrown an error for that too
Jon West
@ddproxy
How did I mess that up...
Derek J. Lambert
@djlambert
what's the first byte?
should be 0 or 1
Jon West
@ddproxy
0
Derek J. Lambert
@djlambert
0x00?
Jon West
@ddproxy
0103000020E610000098000000
But, interesting... The difference between my two files is one is wrapped with "s and the other is not..
Derek J. Lambert
@djlambert
polygon?
Jon West
@ddproxy
Oh yeah
donuts ;)
_
Derek J. Lambert
@djlambert
the byte order is 01 but that's still valid
03 00 00 20 should be polygon with srid
so that doesn't have any strange flags
Jon West
@ddproxy
I'll figure it out tonight, maybe write a CLI tool to debug with...
Need to grab some lunch :S
Samuel Denis-D'Ortun
@sadortun
Hello guys, we could probably close the following issue since they were resolved ; creof/doctrine2-spatial#121creof/doctrine2-spatial#54creof/doctrine2-spatial#128
Derek J. Lambert
@djlambert
#121 has a work around but proxies haven't been implemented yet. I'm not convinced #128 is resolved but not much we can do without more information.
Derek J. Lambert
@djlambert
Currently in wkt-parser and wkb-parser the namespace uses WKT or WKB in all uppercase. The class names in geo-obj are currently CamelCased (Wkt, Wkb). Should I uppercase these to be consistent, or should the "standard" be uppercase namespace, CamelCase classes?
Jon West
@ddproxy
Uh, Uppercase all the things. WKB, WKB are acronyms
Derek J. Lambert
@djlambert
ok thanks. That was my thought on the other libraries. Not sure why I CamelCased it here. lazy fingers
Jon West
@ddproxy
Likewise...
Philippe CARLE
@philippecarle
just wanted to say ¸¸.•¨•♫♪ Thanks ! (it's not enough often in OS world)
Samuel Denis-D'Ortun
@sadortun
@philippecarle :sparkles:
Derek J. Lambert
@djlambert
:)
Philippe CARLE
@philippecarle
hey there
Has someone already benchmarked performance of "usual" spatial operations with this doctrine extension between MySQL 5.7 and PostGIS ?
Samuel Denis-D'Ortun
@sadortun
@philippecarle I would say fast enough ! Working of 5M points, and performance is not a concern for now.
Jon West
@ddproxy
@philippecarle 26M points here... No issues yet.
Peter Juanda
@pjuanda
Hi there, can we add support for sqlite ? If there is an issue with sqlite pdo that forbid us to load extension, we can use custom sqlite dbal that provided in here jsor/dbal-sqlite3
Derek J. Lambert
@djlambert
DBAL won't solve the issue, it's in the PDO driver. https://bugs.php.net/bug.php?id=64810. The only way around this currently is to patch and compile a local copy.
local copy of PHP
Peter Juanda
@pjuanda
@djlambert i think custom dbal will solve the issue. Custom dbal allow you to load an extension for processing the data. Ehm, i have try it, and found the geometry command can be executed perfectly
Derek J. Lambert
@djlambert
do you have any sample code?
Peter Juanda
@pjuanda
currently my implementation still dirty, i just copy the mysql folder with contain the functions to new folder as sqlite, with some tweaking it works.
Derek J. Lambert
@djlambert
for loading the extension in dbal
Peter Juanda
@pjuanda
@djlambert i'll try dig deeper in this weekend, and i'll share it over here