Re: .NET database inspection API?
- From: "Peter Duniho" <NpOeStPeAdM@xxxxxxxxxxxxxxxx>
- Date: Sun, 27 Apr 2008 17:06:01 -0700
On Sun, 27 Apr 2008 15:06:46 -0700, Arne Vajhøj <arne@xxxxxxxxxx> wrote:
[...]True. And the way you would go about accomplishing this would very much be database dependent (unfortunately). The reason is that the meta data within each database (THIS is the stuff you are after) is stored differently for each database product, and even changes between versions for a given database (e.g., SQL Server).
That is how it is.
It is not how it needs to be.
The JDBC API provides a database independent way of doing it. There are
defined methods in the interfaces and the JDBC driver writers has to
implement that using whatever methods are appropriate for the database.
Hmmm...well, that's interesting. In my case, I don't actually _need_ general-purpose database support, at least not at the moment. It just seemed that the more generally the application could be written at the outset, the less likely there'd be some maintenance issue in the future, should the database format change.
I know the database format (Access .MDB files). And I don't _have_ to do this in .NET. Java would be okay, if that turned out to be a better general-purpose solution.
Rather than switch newsgroups, I'll just ask the basic question here: is there JDBC support for Access .MDB files? If so, is this support limited to a specific platform or platforms (e.g. Windows), or have the drivers been implemented wherever the Java run-time itself has been?
Cross-platform would be great. The specific application can be Windows only if that turns out to be the least-expensive way to write it, but the users would much prefer a cross-platform solution. If it's actually easier to do it cross-platform, via Java, then that's an obvious win. :)
The fact is, if push came to shove, there's no real need to be able to deal with an arbitrary database structure. At least for the moment, the actual database structure is known and of course we can always open the files in Access to find out the details of the structure if it should change in the future. It would be sufficient to simply allow the user to describe the database structure. But obviously it'd be easier for the user if the application can present the existing structure to the user instead.
I appreciate all the responses. The DbConnection.GetSchema() method sounds the most promising, at least from the .NET point of view. However, I'm intrigued by the possibility that Java might actually work better. That would be amusingly ironic. :)
Thanks!
Pete
.
- Follow-Ups:
- Re: .NET database inspection API?
- From: Arne Vajhøj
- Re: .NET database inspection API?
- References:
- .NET database inspection API?
- From: Peter Duniho
- Re: .NET database inspection API?
- From: Cramer
- Re: .NET database inspection API?
- From: Arne Vajhøj
- .NET database inspection API?
- Prev by Date: Merge lists
- Next by Date: Re: Link forms (newbie)
- Previous by thread: Re: .NET database inspection API?
- Next by thread: Re: .NET database inspection API?
- Index(es):
Relevant Pages
|