You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by Hugh Brien <hp...@home.com> on 2001/11/21 03:17:35 UTC
IDBroker and Turbine Version
Does TDK support IdBroker for the ID_TABLE using the MSSQL database? or do
I have autoincrement Everything else seems to be working except for this.
Any help would be appreciated. What is the best way to test the IDBroker
functions outside of the web environment, Calling it directly for example
r,
Hugh
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: IDBroker and Turbine Version
Posted by Jason van Zyl <jv...@zenplex.com>.
On 11/21/01 5:21 AM, "Hugh Brien" <hp...@home.com> wrote:
> Thanks for the reply. This helps a lot. I am going to have to think a
> little harder about what pieces of Turbine I am going to use moving forward.
> At this point in time, given that I have to use MSSQL server the questions
> is what is the best combination of TDK, Turbine, Torque. I have CVS
> downloads of all of the projects and I am pretty comfortable with building.
> Much of my confusion has come about because I am working with Jetspeed,
> Turbine, Torque and the TDK 2.1 at the same time.
Yes getting Jetspeed working with standard versions of Turbine can IMO be a
royal PITA but we are trying to align versions. I'm waiting for a message
back from Santiago about any other compatibility problems.
> I wrote a test class for IDBroker. For those of try to get familar with it
> you may want to try it out. You need to supply your own Peer class or just
> use one from Turbine.
If you have a test for the IDBroker can you submit it so that I can include
it in the Torque testbed? If you look at runtime tests in torque you could
cleanup your test below to work with it. Soon you will be able to use the
decoupled Torque within Jetspeed.
>
> package org.apache.turbine.test;
>
> import org.apache.turbine.util.TurbineConfig;
> import org.apache.turbine.services.TurbineServices;
> import org.apache.turbine.util.db.*;
> import com.novuscg.om.portal.*;
> import com.novuscg.om.portal.map.*;
> import java.util.*;
> import java.math.BigDecimal;
>
> public class TestClass
> {
> public static String WEB_DIR = "H:/jakarta-turbine-2";
> public static String CONFIG_FILE = "conf/TurbineResources.properties";
> static
> {
> TurbineConfig tc = new TurbineConfig(WEB_DIR, CONFIG_FILE);
> tc.init();
> }
>
> public void testIDS()
> {
> try
> {
> org.apache.turbine.util.db.map.DatabaseMap dbMap = null;
> // I used a table I had generated from Torque and
> dbMap = GroupProfilePeer.getMapBuilder().getDatabaseMap();
> IDBroker broker = dbMap.getIDBroker();
> for (int i = 0; i < 30; i++)
> {
> String value = broker.getIdAsString(null,
> GroupProfilePeer.TABLE_NAME);
> System.out.println(value);
> }
> }
> catch (Exception ex)
> {
> ex.printStackTrace();
> }
> }
>
> public static void main(String[] args)
> {
> TestClass testClass1 = new TestClass();
> testClass1.testIDS();
> TurbineServices.getInstance().shutdownServices();
> System.exit(0);
>
> }
> }
>
>
> ----- Original Message -----
> From: "Jason van Zyl" <jv...@zenplex.com>
> To: "Turbine Developers List" <tu...@jakarta.apache.org>
> Sent: Tuesday, November 20, 2001 10:15 PM
> Subject: Re: IDBroker and Turbine Version
>
>
>> On 11/21/01 3:16 AM, "Hugh Brien" <hp...@home.com> wrote:
>>
>>> Jason,
>>> Thanks for the response, I am just trying to understand the relationship
>>> between the following, if I get it, I will write a paper on it. The
> error
>>> we got on SQL server under TDK 2.1 was that NEXT_ID was not being
> written to
>>> the ID_TABLE.
>>
>> You are using the decoupled Torque, right? We encountered some problems
>> where the IDBroker wasn't working with Postgres because the SQL generated
>> wasn't something that Postgres liked. If you are getting an SQL error than
>> send us the SQL we definitely could have missed because we haven't tested
>> with MSSQL. Can you successfully run the testbed? That should give you
> some
>> indication of what's going on.
>>
>>> 1. Using IdBroker vs None vs Native vs AutoIncrement
>>
>> There is really only
>>
>> -> IDBroker
>> -> Native
>> -> None
>>
>> Using the "idbroker" the ids are obtained from the IDBroker via a portable
>> mechansim (or getting there :-)).
>>
>> Using "native" means that the target RDB's internal mechanism for
> generating
>> ids will be used. So that's using serial columns in Postgres,
> autoincrement
>> in MySQL and sequences in Oracle. I'm not sure if the "native" method is
>> workng for MSSQL. The MSSQL adapter is a subclass of the DBSybase Adapter
> so
>> you'll probably want to look at that to see if it is generating the
> correct
>> SQL for obtaining ids natively for MSSQL.
>>
>>> 2. Which projects support which type of ID generation
>>>
>>> TDK does ?
>>
>> "idbroker" "none" "native" using decoupled Torque so that's 3.x
>> "idbroker" "none" "autoincrement" "sequence" in 2.x
>>
>>> Jetspeed ?
>>
>> I believe David is going to attempt to use decoupled Torque, he's waiting
>> for me to make it easily available for use in 2.x
>>
>>> Turbine 2 ?
>>
>> uses torque within the 2.x tree.
>>
>>> Turbine 3 ?
>>
>> uses decoupled torque
>>
>>> Torque ?
>>
>> this is the decoupled torque
>>
>>> 3. The main function of IDBroker is to grab values from the IDTABLE,
>>> increment NEXT_ID and optional cache values to minimize database hits.
>>
>> Yes.
>>
>>> 4. IDBroker uses the DB module class to generate IDs? from the source I
>>> think it does.?
>>
>> The IDBroker will use the appropriate database adapter to form the correct
>> SQL to obtain ids if "native" was chosen as the idmethod in the datamodel
>> descriptor.
>>
>>> 5. If IDBroker gets a couple id's at time what happens to unused values.
>>> 6. The idmethod on the ID_TABLE is not relevant if I manually add rows
> to
>>> the ID_TABLE.
>>
>> Never really looked, I imagine they are potentially lost. It's something
> we
>> could improve if the ids are actually lost though in most cases I imagine
> it
>> doesn't matter because the IDBrokers uses will probably be in long lived
>> processes so I imagine the loss of ids is negligible.
>>
>> Hope that answers some questions :-)
>>
>>> r,
>>> Hugh
>>>
>>>
>>>
>>> ----- Original Message -----
>>> From: "Jason van Zyl" <jv...@zenplex.com>
>>> To: "Turbine Developers List" <tu...@jakarta.apache.org>
>>> Sent: Tuesday, November 20, 2001 5:30 PM
>>> Subject: Re: IDBroker and Turbine Version
>>>
>>>
>>>> On 11/20/01 9:17 PM, "Hugh Brien" <hp...@home.com> wrote:
>>>>
>>>>> Does TDK support IdBroker for the ID_TABLE using the MSSQL database?
>>>>
>>>> I do not use MSSQL myself but you should be able to use the IDBroker in
>>>> conjunction with any database. But I wouldn't be surprise if MSSQL
> forced
>>>> you to use the internal Id generation provided by MSSQL.
>>>>
>>>> Are you getting an error? If so what is it?
>>>>
>>>>> or do
>>>>> I have autoincrement Everything else seems to be working except for
>>> this.
>>>>> Any help would be appreciated. What is the best way to test the
>>> IDBroker
>>>>> functions outside of the web environment, Calling it directly for
>>> example
>>>>> r,
>>>>> Hugh
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> To unsubscribe, e-mail:
>>> <ma...@jakarta.apache.org>
>>>>> For additional commands, e-mail:
>>> <ma...@jakarta.apache.org>
>>>>
>>>> --
>>>>
>>>> jvz.
>>>>
>>>> Jason van Zyl
>>>>
>>>> http://tambora.zenplex.org
>>>> http://jakarta.apache.org/turbine
>>>> http://jakarta.apache.org/velocity
>>>> http://jakarta.apache.org/alexandria
>>>> http://jakarta.apache.org/commons
>>>>
>>>>
>>>>
>>>> --
>>>> To unsubscribe, e-mail:
>>> <ma...@jakarta.apache.org>
>>>> For additional commands, e-mail:
>>> <ma...@jakarta.apache.org>
>>>>
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>>
>> --
>>
>> jvz.
>>
>> Jason van Zyl
>>
>> http://tambora.zenplex.org
>> http://jakarta.apache.org/turbine
>> http://jakarta.apache.org/velocity
>> http://jakarta.apache.org/alexandria
>> http://jakarta.apache.org/commons
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: IDBroker and Turbine Version
Posted by Hugh Brien <hp...@home.com>.
Thanks for the reply. This helps a lot. I am going to have to think a
little harder about what pieces of Turbine I am going to use moving forward.
At this point in time, given that I have to use MSSQL server the questions
is what is the best combination of TDK, Turbine, Torque. I have CVS
downloads of all of the projects and I am pretty comfortable with building.
Much of my confusion has come about because I am working with Jetspeed,
Turbine, Torque and the TDK 2.1 at the same time.
I wrote a test class for IDBroker. For those of try to get familar with it
you may want to try it out. You need to supply your own Peer class or just
use one from Turbine.
package org.apache.turbine.test;
import org.apache.turbine.util.TurbineConfig;
import org.apache.turbine.services.TurbineServices;
import org.apache.turbine.util.db.*;
import com.novuscg.om.portal.*;
import com.novuscg.om.portal.map.*;
import java.util.*;
import java.math.BigDecimal;
public class TestClass
{
public static String WEB_DIR = "H:/jakarta-turbine-2";
public static String CONFIG_FILE = "conf/TurbineResources.properties";
static
{
TurbineConfig tc = new TurbineConfig(WEB_DIR, CONFIG_FILE);
tc.init();
}
public void testIDS()
{
try
{
org.apache.turbine.util.db.map.DatabaseMap dbMap = null;
// I used a table I had generated from Torque and
dbMap = GroupProfilePeer.getMapBuilder().getDatabaseMap();
IDBroker broker = dbMap.getIDBroker();
for (int i = 0; i < 30; i++)
{
String value = broker.getIdAsString(null,
GroupProfilePeer.TABLE_NAME);
System.out.println(value);
}
}
catch (Exception ex)
{
ex.printStackTrace();
}
}
public static void main(String[] args)
{
TestClass testClass1 = new TestClass();
testClass1.testIDS();
TurbineServices.getInstance().shutdownServices();
System.exit(0);
}
}
----- Original Message -----
From: "Jason van Zyl" <jv...@zenplex.com>
To: "Turbine Developers List" <tu...@jakarta.apache.org>
Sent: Tuesday, November 20, 2001 10:15 PM
Subject: Re: IDBroker and Turbine Version
> On 11/21/01 3:16 AM, "Hugh Brien" <hp...@home.com> wrote:
>
> > Jason,
> > Thanks for the response, I am just trying to understand the relationship
> > between the following, if I get it, I will write a paper on it. The
error
> > we got on SQL server under TDK 2.1 was that NEXT_ID was not being
written to
> > the ID_TABLE.
>
> You are using the decoupled Torque, right? We encountered some problems
> where the IDBroker wasn't working with Postgres because the SQL generated
> wasn't something that Postgres liked. If you are getting an SQL error than
> send us the SQL we definitely could have missed because we haven't tested
> with MSSQL. Can you successfully run the testbed? That should give you
some
> indication of what's going on.
>
> > 1. Using IdBroker vs None vs Native vs AutoIncrement
>
> There is really only
>
> -> IDBroker
> -> Native
> -> None
>
> Using the "idbroker" the ids are obtained from the IDBroker via a portable
> mechansim (or getting there :-)).
>
> Using "native" means that the target RDB's internal mechanism for
generating
> ids will be used. So that's using serial columns in Postgres,
autoincrement
> in MySQL and sequences in Oracle. I'm not sure if the "native" method is
> workng for MSSQL. The MSSQL adapter is a subclass of the DBSybase Adapter
so
> you'll probably want to look at that to see if it is generating the
correct
> SQL for obtaining ids natively for MSSQL.
>
> > 2. Which projects support which type of ID generation
> >
> > TDK does ?
>
> "idbroker" "none" "native" using decoupled Torque so that's 3.x
> "idbroker" "none" "autoincrement" "sequence" in 2.x
>
> > Jetspeed ?
>
> I believe David is going to attempt to use decoupled Torque, he's waiting
> for me to make it easily available for use in 2.x
>
> > Turbine 2 ?
>
> uses torque within the 2.x tree.
>
> > Turbine 3 ?
>
> uses decoupled torque
>
> > Torque ?
>
> this is the decoupled torque
>
> > 3. The main function of IDBroker is to grab values from the IDTABLE,
> > increment NEXT_ID and optional cache values to minimize database hits.
>
> Yes.
>
> > 4. IDBroker uses the DB module class to generate IDs? from the source I
> > think it does.?
>
> The IDBroker will use the appropriate database adapter to form the correct
> SQL to obtain ids if "native" was chosen as the idmethod in the datamodel
> descriptor.
>
> > 5. If IDBroker gets a couple id's at time what happens to unused values.
> > 6. The idmethod on the ID_TABLE is not relevant if I manually add rows
to
> > the ID_TABLE.
>
> Never really looked, I imagine they are potentially lost. It's something
we
> could improve if the ids are actually lost though in most cases I imagine
it
> doesn't matter because the IDBrokers uses will probably be in long lived
> processes so I imagine the loss of ids is negligible.
>
> Hope that answers some questions :-)
>
> > r,
> > Hugh
> >
> >
> >
> > ----- Original Message -----
> > From: "Jason van Zyl" <jv...@zenplex.com>
> > To: "Turbine Developers List" <tu...@jakarta.apache.org>
> > Sent: Tuesday, November 20, 2001 5:30 PM
> > Subject: Re: IDBroker and Turbine Version
> >
> >
> >> On 11/20/01 9:17 PM, "Hugh Brien" <hp...@home.com> wrote:
> >>
> >>> Does TDK support IdBroker for the ID_TABLE using the MSSQL database?
> >>
> >> I do not use MSSQL myself but you should be able to use the IDBroker in
> >> conjunction with any database. But I wouldn't be surprise if MSSQL
forced
> >> you to use the internal Id generation provided by MSSQL.
> >>
> >> Are you getting an error? If so what is it?
> >>
> >>> or do
> >>> I have autoincrement Everything else seems to be working except for
> > this.
> >>> Any help would be appreciated. What is the best way to test the
> > IDBroker
> >>> functions outside of the web environment, Calling it directly for
> > example
> >>> r,
> >>> Hugh
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> >>> For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >>
> >> --
> >>
> >> jvz.
> >>
> >> Jason van Zyl
> >>
> >> http://tambora.zenplex.org
> >> http://jakarta.apache.org/turbine
> >> http://jakarta.apache.org/velocity
> >> http://jakarta.apache.org/alexandria
> >> http://jakarta.apache.org/commons
> >>
> >>
> >>
> >> --
> >> To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> >> For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >>
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: IDBroker and Turbine Version
Posted by Jason van Zyl <jv...@zenplex.com>.
On 11/21/01 3:16 AM, "Hugh Brien" <hp...@home.com> wrote:
> Jason,
> Thanks for the response, I am just trying to understand the relationship
> between the following, if I get it, I will write a paper on it. The error
> we got on SQL server under TDK 2.1 was that NEXT_ID was not being written to
> the ID_TABLE.
You are using the decoupled Torque, right? We encountered some problems
where the IDBroker wasn't working with Postgres because the SQL generated
wasn't something that Postgres liked. If you are getting an SQL error than
send us the SQL we definitely could have missed because we haven't tested
with MSSQL. Can you successfully run the testbed? That should give you some
indication of what's going on.
> 1. Using IdBroker vs None vs Native vs AutoIncrement
There is really only
-> IDBroker
-> Native
-> None
Using the "idbroker" the ids are obtained from the IDBroker via a portable
mechansim (or getting there :-)).
Using "native" means that the target RDB's internal mechanism for generating
ids will be used. So that's using serial columns in Postgres, autoincrement
in MySQL and sequences in Oracle. I'm not sure if the "native" method is
workng for MSSQL. The MSSQL adapter is a subclass of the DBSybase Adapter so
you'll probably want to look at that to see if it is generating the correct
SQL for obtaining ids natively for MSSQL.
> 2. Which projects support which type of ID generation
>
> TDK does ?
"idbroker" "none" "native" using decoupled Torque so that's 3.x
"idbroker" "none" "autoincrement" "sequence" in 2.x
> Jetspeed ?
I believe David is going to attempt to use decoupled Torque, he's waiting
for me to make it easily available for use in 2.x
> Turbine 2 ?
uses torque within the 2.x tree.
> Turbine 3 ?
uses decoupled torque
> Torque ?
this is the decoupled torque
> 3. The main function of IDBroker is to grab values from the IDTABLE,
> increment NEXT_ID and optional cache values to minimize database hits.
Yes.
> 4. IDBroker uses the DB module class to generate IDs? from the source I
> think it does.?
The IDBroker will use the appropriate database adapter to form the correct
SQL to obtain ids if "native" was chosen as the idmethod in the datamodel
descriptor.
> 5. If IDBroker gets a couple id's at time what happens to unused values.
> 6. The idmethod on the ID_TABLE is not relevant if I manually add rows to
> the ID_TABLE.
Never really looked, I imagine they are potentially lost. It's something we
could improve if the ids are actually lost though in most cases I imagine it
doesn't matter because the IDBrokers uses will probably be in long lived
processes so I imagine the loss of ids is negligible.
Hope that answers some questions :-)
> r,
> Hugh
>
>
>
> ----- Original Message -----
> From: "Jason van Zyl" <jv...@zenplex.com>
> To: "Turbine Developers List" <tu...@jakarta.apache.org>
> Sent: Tuesday, November 20, 2001 5:30 PM
> Subject: Re: IDBroker and Turbine Version
>
>
>> On 11/20/01 9:17 PM, "Hugh Brien" <hp...@home.com> wrote:
>>
>>> Does TDK support IdBroker for the ID_TABLE using the MSSQL database?
>>
>> I do not use MSSQL myself but you should be able to use the IDBroker in
>> conjunction with any database. But I wouldn't be surprise if MSSQL forced
>> you to use the internal Id generation provided by MSSQL.
>>
>> Are you getting an error? If so what is it?
>>
>>> or do
>>> I have autoincrement Everything else seems to be working except for
> this.
>>> Any help would be appreciated. What is the best way to test the
> IDBroker
>>> functions outside of the web environment, Calling it directly for
> example
>>> r,
>>> Hugh
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>>
>> --
>>
>> jvz.
>>
>> Jason van Zyl
>>
>> http://tambora.zenplex.org
>> http://jakarta.apache.org/turbine
>> http://jakarta.apache.org/velocity
>> http://jakarta.apache.org/alexandria
>> http://jakarta.apache.org/commons
>>
>>
>>
>> --
>> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
>> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: IDBroker and Turbine Version
Posted by Hugh Brien <hp...@home.com>.
Jason,
Thanks for the response, I am just trying to understand the relationship
between the following, if I get it, I will write a paper on it. The error
we got on SQL server under TDK 2.1 was that NEXT_ID was not being written to
the ID_TABLE.
1. Using IdBroker vs None vs Native vs AutoIncrement
2. Which projects support which type of ID generation
TDK does ?
Jetspeed ?
Turbine 2 ?
Turbine 3 ?
Torque ?
3. The main function of IDBroker is to grab values from the IDTABLE,
increment NEXT_ID and optional cache values to minimize database hits.
4. IDBroker uses the DB module class to generate IDs? from the source I
think it does.?
5. If IDBroker gets a couple id's at time what happens to unused values.
6. The idmethod on the ID_TABLE is not relevant if I manually add rows to
the ID_TABLE.
r,
Hugh
----- Original Message -----
From: "Jason van Zyl" <jv...@zenplex.com>
To: "Turbine Developers List" <tu...@jakarta.apache.org>
Sent: Tuesday, November 20, 2001 5:30 PM
Subject: Re: IDBroker and Turbine Version
> On 11/20/01 9:17 PM, "Hugh Brien" <hp...@home.com> wrote:
>
> > Does TDK support IdBroker for the ID_TABLE using the MSSQL database?
>
> I do not use MSSQL myself but you should be able to use the IDBroker in
> conjunction with any database. But I wouldn't be surprise if MSSQL forced
> you to use the internal Id generation provided by MSSQL.
>
> Are you getting an error? If so what is it?
>
> > or do
> > I have autoincrement Everything else seems to be working except for
this.
> > Any help would be appreciated. What is the best way to test the
IDBroker
> > functions outside of the web environment, Calling it directly for
example
> > r,
> > Hugh
> >
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
> --
>
> jvz.
>
> Jason van Zyl
>
> http://tambora.zenplex.org
> http://jakarta.apache.org/turbine
> http://jakarta.apache.org/velocity
> http://jakarta.apache.org/alexandria
> http://jakarta.apache.org/commons
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: IDBroker and Turbine Version
Posted by Jason van Zyl <jv...@zenplex.com>.
On 11/20/01 9:17 PM, "Hugh Brien" <hp...@home.com> wrote:
> Does TDK support IdBroker for the ID_TABLE using the MSSQL database?
I do not use MSSQL myself but you should be able to use the IDBroker in
conjunction with any database. But I wouldn't be surprise if MSSQL forced
you to use the internal Id generation provided by MSSQL.
Are you getting an error? If so what is it?
> or do
> I have autoincrement Everything else seems to be working except for this.
> Any help would be appreciated. What is the best way to test the IDBroker
> functions outside of the web environment, Calling it directly for example
> r,
> Hugh
>
>
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
http://tambora.zenplex.org
http://jakarta.apache.org/turbine
http://jakarta.apache.org/velocity
http://jakarta.apache.org/alexandria
http://jakarta.apache.org/commons
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>