Sounds great, thanks.
On Wednesday, 17 July 2013 19:35:48 UTC-7, Michael Bayer wrote:
well we try to get releases out every 4-6 weeks but sometimes it takes
longer.though this issue was a surprise and does lean things towards
releasing sooner.
On Jul 17, 2013, at 12:38 PM, Basil
Hi Michael,
Thanks for your help. Using 0.8.3 and the type variant passes our tests.
Do you have any (even rough) estimate as to when 0.8.3 will be released to
PyPI?
Thanks,
Basil
On Friday, 12 July 2013 18:56:14 UTC-7, Michael Bayer wrote:
Right, DateTime + with_variant() +
well we try to get releases out every 4-6 weeks but sometimes it takes longer.
though this issue was a surprise and does lean things towards releasing
sooner.
On Jul 17, 2013, at 12:38 PM, Basil Veerman bveer...@uvic.ca wrote:
Hi Michael,
Thanks for your help. Using 0.8.3 and the
Hi,
I've been struggling for a while trying to create a mapping that works with
both PostGIS and SQLite databases when dealing with DateTime.
Background: Production PostGIS database has been reduced and converted to a
spatialite database with the same schema for offline testing purposes.
On Jul 12, 2013, at 5:53 PM, Basil Veerman bveer...@uvic.ca wrote:
Hi,
I've been struggling for a while trying to create a mapping that works with
both PostGIS
what's a PostGIS database? do you mean a Postgresql database with spatial
extensions installed?
Background: Production
Here is a short example that illustrates the original error:
*Create Test Database:*
$ sqlite3 testing.sqlite
SQLite version 3.7.13 2012-06-11 02:05:22
Enter .help for instructions
Enter SQL statements terminated with a ;
sqlite BEGIN TRANSACTION;
sqlite CREATE TABLE 'obs_raw' ('obs_raw_id'
Right, DateTime + with_variant() + sqlite.DATETIME with a custom storage format
and regexp. *However*. There's an unfortunate case that the storage
format/regexp arguments, introduced in 0.8.0, are not actually working fully,
and I've just committed the fix. So you'll have to use 0.8.3 for
