I am studying DBMS after a gap of 11+ years. In my days we
used to program in xbase and sometime in the mid 90s came up
this idea of Database Connectivity(DBC) and Client/Server(C/S)
computing.
Is DBC in a C/S framework still the dominant programming
paradigm nowadays? Are any standards in place?
Do we have any surveys on what technologies sound good to invest
programming efforts on from a long-term perspective?
I am sorry for the long list of questions but its natural, I guess
(after having stayed away for so long).

<ada_student@yahoo.comwrote in message
news:1134972037.839053.142850@
>I am studying DBMS after a gap of 11+ years. In my days we
used to program in xbase and sometime in the mid 90s came up
this idea of Database Connectivity(DBC) and Client/Server(C/S)
computing.

Is DBC in a C/S framework still the dominant programming
paradigm nowadays? Are any standards in place?

Yes, though there are some tools to provide layers of abstraction on top of
it, Client/Server is still the underlying architecture.

Do we have any surveys on what technologies sound good to invest
programming efforts on from a long-term perspective?

Depends on the language and platform you're using for application
development.

Microsofty:
http://en.wikipedia.org/wiki/

Javaish:

%28java%29

Most RDBMS implementations offer a low-level proprietary API (or else a
network protocol), and the above standards are typically implemented as
libraries on top of the given implementation's API. So for example you
might have an DBC "driver" for MySQL, which means a library of code
conforming to the DBC API, and implementing the operations in the DBC
specification using MySQL's API. So you'd need a different DBC driver for
each RDBMS brand.

There is virtually no standardization at the client/server network protocol
level, or the proprietary API level.

Regards,
Bill K.

Just a thought, if there are layers of abstraction, then
how do they satisfy the footprint requirements on
embedded platforms?
Is there anything for small footprint(low overhead) platforms?

<ada_student@yahoo.comwrote in message
news:1135049466.713352.311980@
Just a thought, if there are layers of abstraction, then
how do they satisfy the footprint requirements on
embedded platforms?

Is there anything for small footprint(low overhead) platforms?

I thought you were asking about client-server architectures! :-)

Clearly, the large-footprint solutions are usually not appropriate for
compact platforms.
I don't know much about those platforms, so I don't know much about the
state of the art of DBMS solutions.

There's Cloudscape aka Derby, with is an open-source Java-based DBMS
solution that runs on both desktop and mobile platforms.

http://db.apache.org/derby/

Regards,
Bill K.

Thank you! You have been most helpful.