(Tim

You listed "Need to add replication and syncronization capabilities to
DBISAM" on your list of current developments.  Will replication be included
in the initial release of ElevateDB?  Replication is required by my client
AND needed soon.

I understand that you don't wan't to talk too much about the features and
timing of ElevateDB, but I'm considering licensing Context Software's DB
Extensions, primarily for their replication.  If I do, then I may have to...

       Delay migrating to ElevateDB until Context supports ElevateDB
OR
       Delay implementing replication until Context supports ElevateDB
OR
       Reinvent the (replication) wheel

If ElevateDB will support replication, then I can implement ElevateDB and
ElevateDB replication ASAP, letting Context catch up, whenever.
Alternatively, if Context is working in concert with ElevateDB's release and
support will be quick - that could work too!

Chuck Hall

Chuck,

<< You listed "Need to add replication and syncronization capabilities to
DBISAM" on your list of current developments.  Will replication be included
in the initial release of ElevateDB?  >>

I can't say for sure at this point, but it looks like no, at least
initially.  The one item that has a question mark next to it is replication.
EDB is engineered for replication capabilities, meaning that it has
information in the rows and tables that allow it to track versions of rows,
whether replication is enabled, etc.   However, the code still needs some
work.  Also, because cached updates rely on the replication for
functionality, it will also not be available most likely in the initial
release.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

Is this by chance heading towards row versioning like Interbase?

Sean



Tim Young [Elevate Software] wrote:
> EDB is engineered for replication capabilities, meaning that it has
> information in the rows and tables that allow it to track versions of rows,
> whether replication is enabled, etc.   However, the code still needs some
> work.

Yikes! OK, time to backpeddle on one big project of mine.
Does anybody know of a DBMS with most of the great features we all know
and love in DBISAM that does do replication? (Don't worry Tim, just this
one particular project; I will always remain a DBISAM fanatic!)

~Jason Lee


Tim Young [Elevate Software] wrote:
> I can't say for sure at this point, but it looks like no, at least

On the other hand, if the versioning infrastructure will already be part
of the record structure in EDB, then it shouldn't be too big of a
stretch to implement a method of replication myself--right?

~Jason Lee

Jason Lee wrote:
> Yikes! OK, time to backpeddle on one big project of mine.
> Does anybody know of a DBMS with most of the great features we all know
> and love in DBISAM that does do replication? (Don't worry Tim, just this
> one particular project; I will always remain a DBISAM fanatic!)
>
> ~Jason Lee
>
>
> Tim Young [Elevate Software] wrote:
>> I can't say for sure at this point, but it looks like no, at least

Tim Young [Elevate Software] wrote:
....
> I can't say for sure at this point, but it looks like no, at least
> initially.  The one item that has a question mark next to it is
> replication.

Ok, let me get a stick and stir further Are there plans for mirroring?
You know, 2 DBISAM DBs on different machines with the same state, for fault
tolerance? Yes, I know, enterprisish...

Ralf

Sean,

<< Is this by chance heading towards row versioning like Interbase? >>

No, it's a different kind of versioning.  Eventually we do plan on offering
a higher-end server that does multi-versioning, etc. but that will work much
differently than Interbase also.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jason,

<< On the other hand, if the versioning infrastructure will already be part
of the record structure in EDB, then it shouldn't be too big of a stretch to
implement a method of replication myself--right? >>

Unfortunately it isn't visible to the end developer.  It's used internally
to determine when a row was last replicated and whether it has changed since
that time.

--
Tim Young
Elevate Software
www.elevatesoft.com

Ralf,

<< Ok, let me get a stick and stir further Are there plans for
mirroring? You know, 2 DBISAM DBs on different machines with the same state,
for fault tolerance? Yes, I know, enterprisish... >>

Well, it isn't in there natively, but you could certainly do it with
triggers fairly easily, and the table and column constraints will make sure
both database copies are valid at all times.

--
Tim Young
Elevate Software
www.elevatesoft.com

Jason:

You could try DBISAM 4 and ContextSoftware's (www.contextsoft.com) database
extensions like I'm considering.  DBISAM 4 would be a smaller leap to EDB,
once EDB supports replication or ContextSoftware supports both EDB and
replication.  The limited demos, documentation typos, and lack of
newsgroup/forum for ContextSoftware makes me skeptical, but they are
mentioned favorably and often in this newsgroup.

Incidentally, I don't know why my name doesn't show up in the "From" column
in my news reader (Outlook Express).  It is listed in the properties for
this newsgroup.

Chuck Hall


"Jason Lee" <computerguy@wavecable.com> wrote in message
news:8B745973-1BCD-4356-9612-7F9FF6016CB0@news.elevatesoft.com...
> On the other hand, if the versioning infrastructure will already be part
> of the record structure in EDB, then it shouldn't be too big of a stretch
> to implement a method of replication myself--right?
>
> ~Jason Lee
>
> Jason Lee wrote:
>> Yikes! OK, time to backpeddle on one big project of mine.
>> Does anybody know of a DBMS with most of the great features we all know
>> and love in DBISAM that does do replication? (Don't worry Tim, just this
>> one particular project; I will always remain a DBISAM fanatic!)
>>
>> ~Jason Lee
>>
>>
>> Tim Young [Elevate Software] wrote:
>>> I can't say for sure at this point, but it looks like no, at least