#2 Cloudscape5/DB2J Support

closed-accepted
None
5
2003-01-19
2002-10-21
No

IBM seem to have changed the database name, etc. to
db2j from cloudscape. I found this because autocreate
of tables failed for me as it was using an adapter that
supported deferred constraints.

I modified the DatabaseAdapter class and created a
new DB2JAdapter class (the latter I am not sure is
required).

It now seems to work.

Attached is a patch.

Matty.

Discussion

  • Matthew Cooper

    Matthew Cooper - 2002-10-21

    Patch for cloudscape 5 which is now db2j

     
  • Mike Martin

    Mike Martin - 2002-10-25

    Logged In: YES
    user_id=582193

    The separate adapter class isn't required unless DB2J differs
    from Cloudscape in some way (other than name) that TJDO
    would care about, such as support for deferred constraint
    checking or DROP TABLE CASCADE, neither of which was
    supported by the old Cloudscape. Otherwise it could just reuse
    the CloudscapeAdapter.

    You should check on the deferred constraint issue; it's important
    to use it if they now support it. Certain patterns that might occur
    in a user's data object model (typically involving circular
    references) cannot be supported without it.

    Mike

     
  • Mike Martin

    Mike Martin - 2003-01-19
    • assigned_to: nobody --> jackknifebarber
    • status: open --> closed-accepted
     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks