Subject | Re: [ib-support] DBISAM to FB |
---|---|
Author | Paul Schmidt |
Post date | 2003-01-14T13:29:39Z |
On January 13, 2003 06:09 pm, you wrote:
database has them, due to the differences between SQL implementations they
are all slightly different.
Time fields are not supported? The date, time and timestamp fields are all
supported with Dialect 3. As for boolean I usually use a domain, that
defines the characteristics of a boolean.
Autoinc, well we have generators, and in many ways generators are better, a
generator, because it's an independant object can be set to other values. It
operates outside of transaction control, and supports (dialect 3) 64bit
integers.
Index names, I usually pre-pend the table name to indexes anyway, so I didn't
even notice, when the number of indexes gets large, this gets to be an
advantage, because by pre-pending the table name, you know what table the
index belongs to.
If you have to support different engines, then Domains, Triggers and Stored
Procedures can be your best friends, and your worst enemies. Best friends,
in that engine specifics can be implemented using those methods, and worst
enemies, in that they are all different, in their implementation.
> Is anyone aware of any docs relating to this subject... or advice on how toMost of the "problems" are not really problems, reserved words, nearly every
> proceed?
>
> Issues I've come across so far:
> - Reserved Words... oh boy<g>
> - Boolean, Time and AutoInc field types not supported
> - Same Index names, even on different tables, not allowed
database has them, due to the differences between SQL implementations they
are all slightly different.
Time fields are not supported? The date, time and timestamp fields are all
supported with Dialect 3. As for boolean I usually use a domain, that
defines the characteristics of a boolean.
Autoinc, well we have generators, and in many ways generators are better, a
generator, because it's an independant object can be set to other values. It
operates outside of transaction control, and supports (dialect 3) 64bit
integers.
Index names, I usually pre-pend the table name to indexes anyway, so I didn't
even notice, when the number of indexes gets large, this gets to be an
advantage, because by pre-pending the table name, you know what table the
index belongs to.
If you have to support different engines, then Domains, Triggers and Stored
Procedures can be your best friends, and your worst enemies. Best friends,
in that engine specifics can be implemented using those methods, and worst
enemies, in that they are all different, in their implementation.