David Bath wrote:
> There are a couple of philosophical perspectives I've come across in
> previous
> work with cadastral data that may be useful...[snipped]
Thanks, David
In this particular application, structures such as postcode sectors,
administrative boundaries etc. are not really of much i
On Thu, 17 Nov 2005 19:44, Andy Ballingall wrote:
> I've got a database for a website which is a variant of the 'show stuff near
> to me' sort of thing.
>
> Rather than host this database on a single server, I have a scheme in mind
> to break the database up geographically so that each one can run
Hello,
I’ve got a database
for a website which is a variant of the ‘show stuff near to me’
sort of thing.
Rather than host this
database on a single server, I have a scheme in mind to break the database up
geographically so that each one can run comfortably on a small server, but
I’
On Fri, Nov 18, 2005 at 09:09:24AM -, Andy Ballingall wrote:
> That's very interesting! I've not used slony yet, so I'll setup some tests
> and try exactly this mechanism.
If you do this with Slony, and have any success, I know that the
folks on the Slony list would dearly like to hear about i
Thanks Aidan,
That's very interesting! I've not used slony yet, so I'll setup some tests
and try exactly this mechanism.
What I like about it is that the changes that have to occur to either add a
cell or to split an existing cell into two to manage growing traffic have a
localised effect on the
>Andy, i agree with what codeWarrior says.
But if you are interested in replication, dbmirror is very elegant
(altho not as trendy) simple, and highly customizable replication
solution.
I have heavily modified dbmirror to even support
Asynchronous Conditional row grained
Foreign key dependency
Hi again,
I don't think I've explained my idea well enough:
>You might want to consider using latitude and longitude or zip codes or
taking more of a traditional "GIS" approach rather than duplicating data
across redundant databases.
I do use coordinates to position data. The databases aren't
O codeWarrior έγραψε στις Nov 17, 2005 :
> Sounds like a mis-guided approach to me...
>
> You might want to consider using latitude and longitude or zip codes or
> taking more of a traditional "GIS" approach rather than duplicating data
> across redundant databases.
>
> Another issue is that y
Sounds like a mis-guided approach to me...
You might want to consider using latitude and longitude or zip codes or
taking more of a traditional "GIS" approach rather than duplicating data
across redundant databases.
Another issue is that you end up having to query every database to find
proxim
Hello,
I've got a database for a website which is a variant of the 'show stuff near
to me' sort of thing.
Rather than host this database on a single server, I have a scheme in mind
to break the database up geographically so that each one can run comfortably
on a small server, but I'm not sure abo
10 matches
Mail list logo