-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
What steps will reproduce the problem?
1.Running InMemoryProducerExample
2. Goto http://localhost:8887/InMemoryProducerExample.svc/EdmEntityTypes
3.
What is the expected output? What do you see i…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
H2 shows a different behavior if the foreign key constraints are created after
unique constraints. There is no index for the foreign key constraint and when
dropping unique constraint it does no…
-
```
What steps will reproduce the problem?
1. Check out sipdroid SVN
2. run "android update project -p . -t android-8
3. run "ant debug"
What is the expected output? What do you see instead?
expect…