On Wednesday 06 April 2011 14:53:00 Hans Witvliet wrote:
I'm going to have a go with realtime mysql.
Just wondering, most examples i came across while googling, was with 1.6
systems.
So any drastic changes with 1.8.3, table-layout? other pitfalls?
This isn't a pitfall that comes with the
Hi,
I'm going to have a go with realtime mysql.
Just wondering, most examples i came across while googling, was with 1.6
systems.
So any drastic changes with 1.8.3, table-layout? other pitfalls?
hw
--
_
-- Bandwidth and
On 11-04-06 03:53 PM, Hans Witvliet wrote:
I'm going to have a go with realtime mysql.
Just wondering, most examples i came across while googling, was with 1.6
systems.
So any drastic changes with 1.8.3, table-layout? other pitfalls?
I suggest using res_odbc, it has better support. Aside from
On 11-04-06 03:53 PM, Hans Witvliet wrote:
I'm going to have a go with realtime mysql.
Just wondering, most examples i came across while googling, was with 1.6
systems.
So any drastic changes with 1.8.3, table-layout? other pitfalls?
The tables migrate just fine, but you can update them to
On Wed, 2011-04-06 at 13:57 -0700, Jonathan Thurman wrote:
On 11-04-06 03:53 PM, Hans Witvliet wrote:
I'm going to have a go with realtime mysql.
Just wondering, most examples i came across while googling, was with 1.6
systems.
So any drastic changes with 1.8.3, table-layout? other
On Wed, Apr 6, 2011 at 2:59 PM, Hans Witvliet h...@a-domani.nl wrote:
[snip]
I think i have to stick with mysql, as info is coming from other
applications, but perhaps some of the other code can be tweaked.
mysql is nice (lots of tiny programs writen for it), but i'm not
religious attached