Database recommendations

Thread View: comp.sys.next.programmer

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by David Apfelbaum Wed, 26 Aug 1992 02:29

#772

Author: David Apfelbaum
Date: Wed, 26 Aug 1992 02:29

13 lines
890 bytes

It looks like I am going to need to tie together a rather large amount
of data as we convert an existing database's datafiles over to the NeXT.
 DBKit seems to be an ideal solution.  However, that still leaves a
choice of Sybase or Oracle for the underlying database.

So, are there any recomendations?   Advantages or Disadvantages?


            Thanks for your time....

                    -David Apfelbaum.
                     da0g+@andrew.cmu.edu

Re: Database recommendations

#793

Author: Mark Stankus
Date: Wed, 26 Aug 1992 17:27

35 lines
1210 bytes

In article <seaim=y00WA78imGZf@andrew.cmu.edu> da0g+@andrew.cmu.edu (David Apfelbaum) writes:
>
>It looks like I am going to need to tie together a rather large amount
>of data as we convert an existing database's datafiles over to the NeXT.
> DBKit seems to be an ideal solution.  However, that still leaves a
>choice of Sybase or Oracle for the underlying database.
>
>So, are there any recomendations?   Advantages or Disadvantages?
>
>
>            Thanks for your time....
>
>                    -David Apfelbaum.
>                     da0g+@andrew.cmu.edu


Check out ParaBase -- it makes the database use easier
and acts as a front end to Sybase or Oracle.

Mark Stankus












-- 
mstankus
mstankus@oba

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads