[OpenSER-Devel] Defining MySQL foreign key constraint
Henning Westerholt
henning.westerholt at 1und1.de
Thu Jul 19 11:11:03 CEST 2007
On Wednesday 18 July 2007, Dan Pascu wrote:
> > we discussed this topic yesterday in the devel meeting, and decided to
> > stay for now with the functionality neeeded for OpenSER. But extensions
> > to the datatypes are not to hard to implement. Just take a look into
> > the mysql.xsl file, 'column.type' template, and add the needed
> > datatype.
>
> I know it's not hard to add, however I don't want to continuously patch my
> openser with every release. So the question is if we provide a patch for
> this that uses TIMESTAMP for MySQL and fallsback to DATETIME for the
> other databases, will it be included?
Hi,
i understand your concerns. I would be happy if i need to port only one patch
from release to release.. :-)
But i really want to stay with this tool only to the SQL subset that is needed
for openser. If we introduce TIMESTAMP, then we must later also add
CONSTRAINTS, and probably other stuff as well. We already support much more
SQL then e.g. the SER db creation script, from that this version was forked.
To be honest i don't want to create (and support) a generic SQL template
system.
You could use the following definition to create your tables. You get
TIMESTAMP for mysql, and a fallback to the other databases.
<column>
<type db="mysql">TIMESTAMP</type
<type>datetime</type>
..
</column>
Cheers,
Henning
More information about the Devel
mailing list