StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POhelp creating schema sql for hsqldb
primarykey
Id
6772396
data
AcceptedAnswerId
0
AnswerCount
1
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-07-21T06:59:19.370
FavoriteCount
0
LastActivityDate
2011-07-21T12:55:52.933
LastEditDate
2011-07-21T12:11:28.600
LastEditorUserId
855171
OwnerUserId
855171
ParentId
0
PostTypeId
1
Score
2
ViewCount
4318
LastEditorDisplayName
text
Body
I am quite new to database programming and am trying to create a java program to access hsqldb(version2.2.5) using hibernate.I have 3 classes in my program which I mapped to 3 tables as given below. I wanted to create a one-to-one mapping between SaleOrder and Bill. Also, to create a schema for the db, I tried sql create statements. The two tables SALEORDER and BILL have each other's id as a FK.To avoid dependency error between tables during create,I used alter table add constraint statements Now,I want to use drop table statements at the beginning of script.I used the following <pre><code>ALTER TABLE SALEORDER DROP CONSTRAINT FK_SO_BILL; ALTER TABLE SALEORDER DROP CONSTRAINT FK_SO_BUYER; ALTER TABLE BILL DROP CONSTRAINT FK_BILL_SO; ALTER TABLE BILL DROP CONSTRAINT FK_BILL_BUYER; DROP TABLE BUYER IF EXISTS; DROP TABLE SALEORDER IF EXISTS; DROP TABLE BILL IF EXISTS; </code></pre> This however, causes problem when run for the first time(since the to be altered tables don't exist.).I could not find 'IF EXISTS' clause for ALTER TABLE in hsqldb ..So what is the solution?Should I run the create table scripts alone the first time,and add the alter table,drop table statements shown above thereafter?That doesn't sound a clean way. will be grateful for your suggestions, sincerely, Jim The main schema script is <pre><code>CREATE TABLE BUYER( BUYER_ID BIGINT NOT NULL PRIMARY KEY IDENTITY, NAME VARCHAR(100) ); CREATE TABLE SALEORDER( SALEORDER_ID BIGINT NOT NULL PRIMARY KEY IDENTITY, BUYER_ID BIGINT NOT NULL, BILL_ID BIGINT, ); CREATE TABLE BILL( BILL_ID BIGINT NOT NULL PRIMARY KEY IDENTITY, BUYER_ID BIGINT NOT NULL, SALEORDER_ID BIGINT NOT NULL, ); ALTER TABLE SALEORDER ADD CONSTRAINT FK_SO_BILL FOREIGN KEY(BILL_ID) REFERENCES BILL(BILL_ID); ALTER TABLE SALEORDER ADD CONSTRAINT FK_SO_BUYER FOREIGN KEY(BUYER_ID) REFERENCES BUYER(BUYER_ID); ALTER TABLE BILL ADD CONSTRAINT FK_BILL_BUYER FOREIGN KEY(BUYER_ID) REFERENCES BUYER(BUYER_ID); ALTER TABLE BILL ADD CONSTRAINT FK_BILL_SO FOREIGN KEY(SALEORDER_ID) REFERENCES SALEORDER(SALEORDER_ID); </code></pre> Also,I am using an ant target to create schema <pre><code><target name="createschema" description="execute schema"> <sql driver="${db.driver}" url="${db.url}" userid="${db.username}" password="${db.password}" print="yes" src="${dir.schema}/${file.schema}" caching="false" showheaders="true" > <classpath> <path location="${dir.lib}/hsqldb.jar"/> </classpath> </sql> </target> </code></pre>
Tags
<schema><hsqldb>
Title
help creating schema sql for hsqldb
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USjimgardener
UserOwnerUserId
1. USjimgardener
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POhelp creating schema sql for hsqldb
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POhelp creating schema sql for hsqldb
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.