I came to Toad Modeler from years with its predecessor, Charon’s Case Studio2. I loved CS but, alas, it was purchased by Quest and support stopped at PG 8.2
I’ve run into several problems with Toad which I’m hoping is just a matter of my unfamiliarity with it.
First, in the Entity Properties editor, the Data Type pulldown is only like 9 characters wide so half the datatypes are truncated. For instance, I have four "Timestar"s in the pulldown, which are actually four different types of PG “timestamp” types. And because the columns in the editor aren’t expandable the only way I can tell if I’ve selected the correct data type is to save the data type semi-blindly and do a SQL Preview to make sure I got the right one.
SQL Preview exposed another problem with FK relationships. Like Case Studio, Toad supports Identifying and Non-Identifying relationships but Toad is generating some bizarre SQL with the latter. Here’s what I see when I create a Non-Identifying relationship on “book_id”:
– Table social_referral
CREATE TABLE “social_referral”(
“id” Serial NOT NULL,
“href” Varchar NOT NULL,
“created_at” Timestamp with time zone DEFAULT NOW(),
“site_type” Varchar NOT NULL,
“book_id” Integer DEFAULT nextval(‘book_id_seq’::regclass) NOT NULL,
CONSTRAINT “social_referral__site_type_check” CHECK (site_type::text = ANY (ARRAY[‘facebook’::text, ‘twitter’::text, ‘linkedin’::text, ‘blog’::text, ‘other’::text]))
– Add keys for table social_referral
ALTER TABLE “social_referral” ADD CONSTRAINT “Key4” PRIMARY KEY (“id”,“book_id”)
Not only don’t I see the constraint code for foreign key creation, why is it defaulting book_id with nextval(‘book_id_seq’::regclass)? That’s just going to cycle the sequence table on ‘book’, which is definitely incorrect.
Also, is there anyway to move the knots/ties on the relationship lines? Toad seems to want to place them where it wants to, not where I want them.