Home » Eclipse Projects » Technology Project and PMC » [STELLATION] mysql+innoDB
|
| Re: [STELLATION] mysql+innoDB [message #1318 is a reply to message #1229] |
Fri, 05 July 2002 16:05   |
 Mark C. Chu-Carroll
Messages: 64
Registered: July 2009 |
Member |
|
|
On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
> Hello,
> I've just read the content of the new subproject Stellation...It is very
> interesting... Unlikely it is working only on UNIX platforms. I would
> suggest to use MySQL instead of postgresSQL by adding to MySQL the
> INNODB transactionnal feature...
At the time I started the Stellation project, the transaction support
in MySQL simply wasn't up to what we needed. Based on your message, I
went and took a look at the latest material from InnoDB. It looks like
InnoDB is likely to provide sufficient support for Stellation.
At the moment, our group at IBM is three people, and to be honest, we're
already very over-worked. We would *love* to see someone add InnoDB
support to Stellation. It would likely dramatically improve the
performance of our system. (We're currently significantly slowed down
by some bugs in PostgreSQL JDBC.)
We've got the database specific code pretty tightly encapsulated
in our source. If someone is interested in working on it,
we'll be glad to help show you exactly where all of the database
specific stuff is, and what you'd need to do to add support for a new
database.
It's probably a weeks hacking for someone who's familiar with MySQL. The
biggest piece of work is probably adding documentation for MySQL to the
manuals.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
|
| Re: [STELLATION] mysql+innoDB [message #2140 is a reply to message #1318] |
Fri, 05 July 2002 18:43 |
Eclipse User |
|
|
|
Originally posted by: jrimmer.nospam.irth.net
I, and perhaps others, may be interested in undertaking this task as I
also see the dependence/reliance on Postgress to be a negative. Would
you mind posting the details for implementing support of a new database
in this forum? It would serve as a type of documentation as well as
saving you the hassle of having to repeat yourself.
I'm also entertaining the idea of porting to other databases such as
the embedded version of McKoi, http://www.mckoi.com, which would create
a unified single process (no dependence on other processes) SCM system.
Mark C. Chu-Carroll wrote:
> On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
>
>
>>Hello,
>>I've just read the content of the new subproject Stellation...It is very
>>interesting... Unlikely it is working only on UNIX platforms. I would
>>suggest to use MySQL instead of postgresSQL by adding to MySQL the
>>INNODB transactionnal feature...
>
>
> At the time I started the Stellation project, the transaction support
> in MySQL simply wasn't up to what we needed. Based on your message, I
> went and took a look at the latest material from InnoDB. It looks like
> InnoDB is likely to provide sufficient support for Stellation.
>
> At the moment, our group at IBM is three people, and to be honest, we're
> already very over-worked. We would *love* to see someone add InnoDB
> support to Stellation. It would likely dramatically improve the
> performance of our system. (We're currently significantly slowed down
> by some bugs in PostgreSQL JDBC.)
>
> We've got the database specific code pretty tightly encapsulated
> in our source. If someone is interested in working on it,
> we'll be glad to help show you exactly where all of the database
> specific stuff is, and what you'd need to do to add support for a new
> database.
>
> It's probably a weeks hacking for someone who's familiar with MySQL. The
> biggest piece of work is probably adding documentation for MySQL to the
> manuals.
>
> -Mark
>
--
Jason Rimmer
jrimmer_at_irth.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #2193 is a reply to message #1318] |
Fri, 05 July 2002 23:05 |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Is there some issue with adding a standard MySQL extension to Stellation? I
assuming you're using CPL. The MySQL most people use is GPL. GPL and CPL
don't mix.
Bob
"Mark C. Chu-Carroll" <markcc@bestweb.net> wrote in message
news:ag4ehs$q7u$1@rogue.oti.com...
> On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
>
> > Hello,
> > I've just read the content of the new subproject Stellation...It is very
> > interesting... Unlikely it is working only on UNIX platforms. I would
> > suggest to use MySQL instead of postgresSQL by adding to MySQL the
> > INNODB transactionnal feature...
>
> At the time I started the Stellation project, the transaction support
> in MySQL simply wasn't up to what we needed. Based on your message, I
> went and took a look at the latest material from InnoDB. It looks like
> InnoDB is likely to provide sufficient support for Stellation.
>
> At the moment, our group at IBM is three people, and to be honest, we're
> already very over-worked. We would *love* to see someone add InnoDB
> support to Stellation. It would likely dramatically improve the
> performance of our system. (We're currently significantly slowed down
> by some bugs in PostgreSQL JDBC.)
>
> We've got the database specific code pretty tightly encapsulated
> in our source. If someone is interested in working on it,
> we'll be glad to help show you exactly where all of the database
> specific stuff is, and what you'd need to do to add support for a new
> database.
>
> It's probably a weeks hacking for someone who's familiar with MySQL. The
> biggest piece of work is probably adding documentation for MySQL to the
> manuals.
>
> -Mark
>
> --
> Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
> *** The Stellation project: Advanced SCM for Collaboration
> *** http://www.eclipse.org/stellation
> *** Work Email: mcc@watson.ibm.com ------- Personal Email:
markcc@bestweb.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #2249 is a reply to message #2140] |
Fri, 05 July 2002 23:56 |
Mark C. Chu-Carroll
Messages: 64
Registered: July 2009 |
Member |
|
|
On Fri, 05 Jul 2002 14:43:09 -0400, Jason Rimmer wrote:
> I, and perhaps others, may be interested in undertaking this task as I
> also see the dependence/reliance on Postgress to be a negative. Would
> you mind posting the details for implementing support of a new database
> in this forum? It would serve as a type of documentation as well as
> saving you the hassle of having to repeat yourself.
Here's the summary. If you want to discuss it,
I think the Stellation mailing list is likely a better place.
There are two places that need to be updated: the repository
core, and the workspace. (The workspace, for us, covers the
command-line tools to support a workspace.)
The repository core is implemented in org.eclipse.stellation.repos, and
org.eclipse.stellation.repos.artifacts. For the repository core, the
bulk of database dependent code is encapsulated in what we call an
AccessPoint. An access point is the system that provides all access to
the database, generates handles for accessing a repository, and manages
authentication. There's a generic implementation of an AccessPoint
called DBAccessPoint, which parameterizes most of the DB dependent code.
Then there are database specific subclasses of DBAccessPoint. We have
two versions: PostgresAccessPoint, and DB2AccessPoint. If you look at
DBAccessPoint and its two concrete implementations, you should be able
to figure out how to write a MySQL variant.
The other place in the repository core is in what we call Artifact
Agents. This is one of the more unusual pieces of Stellation. Instead
of hardwiring particular kinds of artifacts into the repository, we
have a generic extension point called an Agent that provides everything needed to
support a particular kind of repository artifact. The SQL code for
retrieving and storing a particular kind of artifact is in the artifact
agent. We try to parameterize it as much as possible through the access
points. You'll need to look at the ArtifactAgent types, and see if they
need any SQL customization for MySQL. The SQL is very obvious in the
files, and it should be easy to read and parameterize if necessary.
Finally, you'll need to modify the server, command-line, and
GUI, to allow them to determine what kind of access point they
should use.
For the command-line, that's the class
org.eclipse.stellation.workspace.Location. It determines the kind
of access point to create based on the prefix of its location
parameter.
For the server, it's in the parameter processing code in
org.eclipse.stellation.repos.messaging.server.Server.Again, it's
a simple conditional on the prefix of the location parameter.
For the UI, I'm afraid I need to defer to my coworker Jim Wright,
who can tell you where in the UI it handles AccessPoint creation.
So far, I've spent all of my time working on the repository side,
so I'm just not sufficiently familiar with how Jim handles this in
the UI. I expect it's very similar, except that Jim build some
GUI support for creatin
> I'm also entertaining the idea of porting to other databases such as
> the embedded version of McKoi, http://www.mckoi.com, which would create
> a unified single process (no dependence on other processes) SCM.
I don't think that we can legally do that. McKoi is GPL, and Stellation
is CPL. Linking them together into a single running process will be a
violation of the GPL.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
| | | |
| Re: [STELLATION] mysql+innoDB [message #23490 is a reply to message #21820] |
Thu, 12 September 2002 09:45 |
Mark C. Chu-Carroll
Messages: 32
Registered: July 2009 |
Member |
|
|
On Fri, 06 Sep 2002 21:56:28 +0000, Werner Punz wrote:
> "Mark C. Chu-Carroll" <markcc@bestweb.net> wrote in news:ag5a54$59k$1
> @rogue.oti.com:
>
>
>> I don't think that we can legally do that. McKoi is GPL, and Stellation
>> is CPL. Linking them together into a single running process will be a
>> violation of the GPL.
>>
>>
> Sorry, to jump in that late. IŽm in the long term process of removing
> CVS
> :-), and Stellation might develop into something neat. Anyway back to
> :the
> GPL problem. You might consider adding the support but leaving the GPL
> part out, but providing a working make file and instructions. Then you
> can leave it up to the user on how to handle the licensing issue. Anyway
> I didnŽt know that Stellation already was usable, I will have a look at
> it seriously.
That's not sufficient. I'm not a lawyer, so I don't fully understand
the hows or whys. But if we distribute code that relies on being linked
specifically to something GPL, then we are just as contaminated by the
GPL as if we included the GPL code. It's something to due with the
precise legal definition of a derived work. Under the GPL, we'd still
be a derived work (or at least that's how I understand what the legal
folks explained to me.)
So we cannot provide support for McKoi, and if someone contributed
a McKoi interface component, we could not put it in our repository.
Sorry.
By the way, there's now an eclipse.technology.stellation. I've
crossposted this there, and I'd prefer to continue the discussion
on that group, where there's a lot less noise.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #28993 is a reply to message #28954] |
Tue, 01 October 2002 21:08 |
Mark C. Chu-Carroll
Messages: 32
Registered: July 2009 |
Member |
|
|
On Tue, 01 Oct 2002 23:13:23 +0000, Werner Keil wrote:
> What IS McKoi?
McKoi is a lightweight open-source database written entirely in Java.
It's got the somewhat neat property that the database is implemented
entirely as a library, and can be linked directly into your program. So
instead of the typical database situation where you run a database
server, and then connect to it as a client through the network, you're
linked directly against the database.
For Stellation purposes, we can't use it, because it's GPL, and it
links directly into the system.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
|
| Re: [STELLATION] mysql+innoDB [message #566082 is a reply to message #1229] |
Fri, 05 July 2002 16:05 |
Mark C. Chu-Carroll
Messages: 64
Registered: July 2009 |
Member |
|
|
On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
> Hello,
> I've just read the content of the new subproject Stellation...It is very
> interesting... Unlikely it is working only on UNIX platforms. I would
> suggest to use MySQL instead of postgresSQL by adding to MySQL the
> INNODB transactionnal feature...
At the time I started the Stellation project, the transaction support
in MySQL simply wasn't up to what we needed. Based on your message, I
went and took a look at the latest material from InnoDB. It looks like
InnoDB is likely to provide sufficient support for Stellation.
At the moment, our group at IBM is three people, and to be honest, we're
already very over-worked. We would *love* to see someone add InnoDB
support to Stellation. It would likely dramatically improve the
performance of our system. (We're currently significantly slowed down
by some bugs in PostgreSQL JDBC.)
We've got the database specific code pretty tightly encapsulated
in our source. If someone is interested in working on it,
we'll be glad to help show you exactly where all of the database
specific stuff is, and what you'd need to do to add support for a new
database.
It's probably a weeks hacking for someone who's familiar with MySQL. The
biggest piece of work is probably adding documentation for MySQL to the
manuals.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
|
| Re: [STELLATION] mysql+innoDB [message #566109 is a reply to message #1318] |
Fri, 05 July 2002 18:43 |
Jason Rimmer
Messages: 1
Registered: July 2009 |
Junior Member |
|
|
I, and perhaps others, may be interested in undertaking this task as I
also see the dependence/reliance on Postgress to be a negative. Would
you mind posting the details for implementing support of a new database
in this forum? It would serve as a type of documentation as well as
saving you the hassle of having to repeat yourself.
I'm also entertaining the idea of porting to other databases such as
the embedded version of McKoi, http://www.mckoi.com, which would create
a unified single process (no dependence on other processes) SCM system.
Mark C. Chu-Carroll wrote:
> On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
>
>
>>Hello,
>>I've just read the content of the new subproject Stellation...It is very
>>interesting... Unlikely it is working only on UNIX platforms. I would
>>suggest to use MySQL instead of postgresSQL by adding to MySQL the
>>INNODB transactionnal feature...
>
>
> At the time I started the Stellation project, the transaction support
> in MySQL simply wasn't up to what we needed. Based on your message, I
> went and took a look at the latest material from InnoDB. It looks like
> InnoDB is likely to provide sufficient support for Stellation.
>
> At the moment, our group at IBM is three people, and to be honest, we're
> already very over-worked. We would *love* to see someone add InnoDB
> support to Stellation. It would likely dramatically improve the
> performance of our system. (We're currently significantly slowed down
> by some bugs in PostgreSQL JDBC.)
>
> We've got the database specific code pretty tightly encapsulated
> in our source. If someone is interested in working on it,
> we'll be glad to help show you exactly where all of the database
> specific stuff is, and what you'd need to do to add support for a new
> database.
>
> It's probably a weeks hacking for someone who's familiar with MySQL. The
> biggest piece of work is probably adding documentation for MySQL to the
> manuals.
>
> -Mark
>
--
Jason Rimmer
jrimmer_at_irth.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #566171 is a reply to message #1318] |
Fri, 05 July 2002 23:05 |
| Eclipse User |
|
|
|
Originally posted by: bob.objfac.com
Is there some issue with adding a standard MySQL extension to Stellation? I
assuming you're using CPL. The MySQL most people use is GPL. GPL and CPL
don't mix.
Bob
"Mark C. Chu-Carroll" <markcc@bestweb.net> wrote in message
news:ag4ehs$q7u$1@rogue.oti.com...
> On Fri, 05 Jul 2002 03:03:03 -0400, xme wrote:
>
> > Hello,
> > I've just read the content of the new subproject Stellation...It is very
> > interesting... Unlikely it is working only on UNIX platforms. I would
> > suggest to use MySQL instead of postgresSQL by adding to MySQL the
> > INNODB transactionnal feature...
>
> At the time I started the Stellation project, the transaction support
> in MySQL simply wasn't up to what we needed. Based on your message, I
> went and took a look at the latest material from InnoDB. It looks like
> InnoDB is likely to provide sufficient support for Stellation.
>
> At the moment, our group at IBM is three people, and to be honest, we're
> already very over-worked. We would *love* to see someone add InnoDB
> support to Stellation. It would likely dramatically improve the
> performance of our system. (We're currently significantly slowed down
> by some bugs in PostgreSQL JDBC.)
>
> We've got the database specific code pretty tightly encapsulated
> in our source. If someone is interested in working on it,
> we'll be glad to help show you exactly where all of the database
> specific stuff is, and what you'd need to do to add support for a new
> database.
>
> It's probably a weeks hacking for someone who's familiar with MySQL. The
> biggest piece of work is probably adding documentation for MySQL to the
> manuals.
>
> -Mark
>
> --
> Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
> *** The Stellation project: Advanced SCM for Collaboration
> *** http://www.eclipse.org/stellation
> *** Work Email: mcc@watson.ibm.com ------- Personal Email:
markcc@bestweb.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #566206 is a reply to message #2140] |
Fri, 05 July 2002 23:56 |
Mark C. Chu-Carroll
Messages: 64
Registered: July 2009 |
Member |
|
|
On Fri, 05 Jul 2002 14:43:09 -0400, Jason Rimmer wrote:
> I, and perhaps others, may be interested in undertaking this task as I
> also see the dependence/reliance on Postgress to be a negative. Would
> you mind posting the details for implementing support of a new database
> in this forum? It would serve as a type of documentation as well as
> saving you the hassle of having to repeat yourself.
Here's the summary. If you want to discuss it,
I think the Stellation mailing list is likely a better place.
There are two places that need to be updated: the repository
core, and the workspace. (The workspace, for us, covers the
command-line tools to support a workspace.)
The repository core is implemented in org.eclipse.stellation.repos, and
org.eclipse.stellation.repos.artifacts. For the repository core, the
bulk of database dependent code is encapsulated in what we call an
AccessPoint. An access point is the system that provides all access to
the database, generates handles for accessing a repository, and manages
authentication. There's a generic implementation of an AccessPoint
called DBAccessPoint, which parameterizes most of the DB dependent code.
Then there are database specific subclasses of DBAccessPoint. We have
two versions: PostgresAccessPoint, and DB2AccessPoint. If you look at
DBAccessPoint and its two concrete implementations, you should be able
to figure out how to write a MySQL variant.
The other place in the repository core is in what we call Artifact
Agents. This is one of the more unusual pieces of Stellation. Instead
of hardwiring particular kinds of artifacts into the repository, we
have a generic extension point called an Agent that provides everything needed to
support a particular kind of repository artifact. The SQL code for
retrieving and storing a particular kind of artifact is in the artifact
agent. We try to parameterize it as much as possible through the access
points. You'll need to look at the ArtifactAgent types, and see if they
need any SQL customization for MySQL. The SQL is very obvious in the
files, and it should be easy to read and parameterize if necessary.
Finally, you'll need to modify the server, command-line, and
GUI, to allow them to determine what kind of access point they
should use.
For the command-line, that's the class
org.eclipse.stellation.workspace.Location. It determines the kind
of access point to create based on the prefix of its location
parameter.
For the server, it's in the parameter processing code in
org.eclipse.stellation.repos.messaging.server.Server.Again, it's
a simple conditional on the prefix of the location parameter.
For the UI, I'm afraid I need to defer to my coworker Jim Wright,
who can tell you where in the UI it handles AccessPoint creation.
So far, I've spent all of my time working on the repository side,
so I'm just not sufficiently familiar with how Jim handles this in
the UI. I expect it's very similar, except that Jim build some
GUI support for creatin
> I'm also entertaining the idea of porting to other databases such as
> the embedded version of McKoi, http://www.mckoi.com, which would create
> a unified single process (no dependence on other processes) SCM.
I don't think that we can legally do that. McKoi is GPL, and Stellation
is CPL. Linking them together into a single running process will be a
violation of the GPL.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
| | | |
| Re: [STELLATION] mysql+innoDB [message #581682 is a reply to message #21820] |
Thu, 12 September 2002 09:45 |
Mark C. Chu-Carroll
Messages: 32
Registered: July 2009 |
Member |
|
|
On Fri, 06 Sep 2002 21:56:28 +0000, Werner Punz wrote:
> "Mark C. Chu-Carroll" <markcc@bestweb.net> wrote in news:ag5a54$59k$1
> @rogue.oti.com:
>
>
>> I don't think that we can legally do that. McKoi is GPL, and Stellation
>> is CPL. Linking them together into a single running process will be a
>> violation of the GPL.
>>
>>
> Sorry, to jump in that late. IŽm in the long term process of removing
> CVS
> :-), and Stellation might develop into something neat. Anyway back to
> :the
> GPL problem. You might consider adding the support but leaving the GPL
> part out, but providing a working make file and instructions. Then you
> can leave it up to the user on how to handle the licensing issue. Anyway
> I didnŽt know that Stellation already was usable, I will have a look at
> it seriously.
That's not sufficient. I'm not a lawyer, so I don't fully understand
the hows or whys. But if we distribute code that relies on being linked
specifically to something GPL, then we are just as contaminated by the
GPL as if we included the GPL code. It's something to due with the
precise legal definition of a derived work. Under the GPL, we'd still
be a derived work (or at least that's how I understand what the legal
folks explained to me.)
So we cannot provide support for McKoi, and if someone contributed
a McKoi interface component, we could not put it in our repository.
Sorry.
By the way, there's now an eclipse.technology.stellation. I've
crossposted this there, and I'd prefer to continue the discussion
on that group, where there's a lot less noise.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
| |
| Re: [STELLATION] mysql+innoDB [message #583847 is a reply to message #28954] |
Tue, 01 October 2002 21:08 |
Mark C. Chu-Carroll
Messages: 32
Registered: July 2009 |
Member |
|
|
On Tue, 01 Oct 2002 23:13:23 +0000, Werner Keil wrote:
> What IS McKoi?
McKoi is a lightweight open-source database written entirely in Java.
It's got the somewhat neat property that the database is implemented
entirely as a library, and can be linked directly into your program. So
instead of the typical database situation where you run a database
server, and then connect to it as a client through the network, you're
linked directly against the database.
For Stellation purposes, we can't use it, because it's GPL, and it
links directly into the system.
-Mark
--
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: mcc@watson.ibm.com ------- Personal Email: markcc@bestweb.net
|
|
|
Goto Forum:
Current Time: Sat Jul 27 12:31:52 GMT 2024
Powered by FUDForum. Page generated in 0.05955 seconds |
] 
Search
Help
Register
Login
Home
