On Feb 7, 8:06 am, Tim Chase <django.us...@tim.thechases.com> wrote:
> PostgreSQL has built-in GIS data-types and functions, which I
> believe are required for theGeoDjangofunctionality (or Oracle).
>   PG also allows flexible creation of new data-types and
> functions/operators as shown by the GIS data-types that were
> integrated early.  It also offers some under-the-covers stunts
> with table-inheritance.  It's very close to Oracle syntax (from
> what I understand, having never used Oracle), so Oracle admins
> may feel more at home in PG.

Just a correction here -- MySQL actually has the GIS types built-in,
whereas with Postgres you have to install the PostGIS extension.
However, the PostGIS types and functions are feature-complete and
compliant with the relevant GIS standards, whereas the built-in MySQL
implementation is half-baked and non-compliant (e.g., no spatial
indexes on InnoDB tables, MBR-only functions, no distance
calculations).

> I personally find MySQL easier to administer, but MySQL has a
> reputation as being built for developers, while PosgreSQL has a
> reputation as being built for DBAs.  I'm a developer first.

I was once a MySQL user, but quite frankly I've become quite alarmed
at MySQL's attitude towards data integrity -- I just don't totally
trust it anymore.  With two botched releases in a row containing
critical bugs (5.0 and 5.1), my impression hasn't improved.  I'm a
developer who cares about his and his client's data first.

> So I can't really recommend one vs. the other unless I knew your
> needs.  Do you needGeoDjango, custom data-types,
> table-inheritance or "enterprise"y features for your DBA, then
> PostgreSQL may be a better choice.  Do you need flexibility in
> storage-engine choice, ready availability on shared/inexpensive
> web hosts, or spiffy GUI/web admin interfaces, then use MySQL.

There's also pgAdmin III, a GUI interface available for PostgreSQL,
and installed by default with the windows installers.

Regardless, I second the opinion to develop for both so one can make
their own judgment to which best suits their needs.

Regards,
-Justin


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to