Don't forget that this already HAS government support, in theory: John Howard has personnally made a deal with the head of family first for preferences, and has has said in public that he will "consult" with them on all policy matters.
Ingres is at its heart a very solid product, although it has a lot of nagging little foibles, and its managament interface is truly awful and primitive.
It is considerably stronger at its heart than MySQL and Posgresql, with a very powerful and robust query engine coupled to an excellent transactional framework.
Compared to Oracle, it's about where Oracle was in the early 90's. The main philosophical difference between Ingres and Oracle is that Ingres tries to use the resources of the underlying OS more (particularly I/O). This manifests in things such as Ingres storing tables as one or more unix files in a directory, whereas Oracle liked to make one big file and manage space within it. When they were direct competitors, Ingres was more geeky and was widely seen to be more agile, flexible and way less resource hungry.
As the RDBMS market changed, Ingres never kept up, particularly on the managebility side of things, and the product suffered badly from the company spending years trying to figure out what to do with it. The current version of Ingres, usually known as OpenIngres II 2.x (which says something about the power of marketing divisions) is essentially the same as 6.4/05 which was in use in the mid 90's.
If they are doing it right, very hard. It's not simply a matter of counting the votes - that's the easy part of the process. The rest of the process includes managing the rolls of enrolled voters, getting them printed so that names can be checked off , collecting those marked up rolls and verifying that everybody has voted and nobody has voted more than once, producing vast amounts of statistics. Oh, and then worrying about who gets to see which parts of the roll when because of privacy considerations. And yes please, can we all have it done by Thursday?
I've been involved in writing code for parts of this process several times over the last two decades, and it actually is hard.
Don't forget that this already HAS government support, in theory: John Howard has personnally made a deal with the head of family first for preferences, and has has said in public that he will "consult" with them on all policy matters.
9 61847842.html?oneclick=true
http://www.theage.com.au/articles/2004/09/24/1095
Ingres is at its heart a very solid product, although it has a lot of nagging little foibles, and its managament interface is truly awful and primitive. It is considerably stronger at its heart than MySQL and Posgresql, with a very powerful and robust query engine coupled to an excellent transactional framework. Compared to Oracle, it's about where Oracle was in the early 90's. The main philosophical difference between Ingres and Oracle is that Ingres tries to use the resources of the underlying OS more (particularly I/O). This manifests in things such as Ingres storing tables as one or more unix files in a directory, whereas Oracle liked to make one big file and manage space within it. When they were direct competitors, Ingres was more geeky and was widely seen to be more agile, flexible and way less resource hungry. As the RDBMS market changed, Ingres never kept up, particularly on the managebility side of things, and the product suffered badly from the company spending years trying to figure out what to do with it. The current version of Ingres, usually known as OpenIngres II 2.x (which says something about the power of marketing divisions) is essentially the same as 6.4/05 which was in use in the mid 90's.
If they are doing it right, very hard. It's not simply a matter of counting the votes - that's the easy part of the process. The rest of the process includes managing the rolls of enrolled voters, getting them printed so that names can be checked off , collecting those marked up rolls and verifying that everybody has voted and nobody has voted more than once, producing vast amounts of statistics. Oh, and then worrying about who gets to see which parts of the roll when because of privacy considerations. And yes please, can we all have it done by Thursday? I've been involved in writing code for parts of this process several times over the last two decades, and it actually is hard.