Samuel R. Neff schrieb:
SQLite's typelessness is an asset if you work only with SQLite but in any application that uses multiple database engines of which SQLite is only one supported engine, the non-standard typelessness is something that has to be worked around. I for one would be in favor of an option to enforce strict typing (compile time option).
Quite true for many cases. Strict typing would help in many cases when using or maintaining wrappers, especially concerning the results of expressions like CAST where there is no meaningful defined type. But your wrong about the 'if working with multiple database engines' generalization. Its more of a language feature, e.g. in Tcl you nearly always have typeless interfaces and it works fine, even when accessing multiple databases (oracle, postgres, mysql + sqlite for example). (the typed interfaces break more often, e.g. Windows COM scripting with VARIANTS). So as a compile time option it would surely be a great addition for all those that have to maintain wrappers. Michael -- Michael Schlenker Software Engineer CONTACT Software GmbH Tel.: +49 (421) 20153-80 Wiener Straße 1-3 Fax: +49 (421) 20153-41 28359 Bremen http://www.contact.de/ E-Mail: [EMAIL PROTECTED] Sitz der Gesellschaft: Bremen | Geschäftsführer: Karl Heinz Zachries Eingetragen im Handelsregister des Amtsgerichts Bremen unter HRB 13215 ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
