Yes, the schema is coming from a SQLServer db. The column is:
[SelectOption]
Col1=Name varchar 50
Col2=Text varchar 30
Col3=Value varchar 50
Col4=ListPosition int 4
I was afraid that you'd say I'd have to change the SQLServer schema = DOH! ;)
Thanks bill!
william graham wrote:
> Hi, Jason --
>
> The problem is that TEXT in InstantDB is a synonym for the binary
> datatype ( see
> http://instantdb.enhydra.org/software/documentation/types.html ).
>
> As far as turning this off, I'm not sure there's a way (anyone else?).
> There is a strictLiterals parm in the db properties, but that prevents
> literals from being interpreted as numerics or as column names.
>
> Is this schema coming from a SQLServer db? If so, I'm a bit surprised,
> since TEXT is a datatype name in SQLServer as well ...
>
> Unless someone on the list has a better idea (which they very well
> may!!), IMHO the column name needs to be changed: hopefully this won't
> wreak havoc with existing code!
>
> Regards,
> Bill Graham
>
> > I am wondering if there is a way to 'turn off' this error checking (I
> > didn't see Text as a keyword in my SQL 92 book), or will I have to
> > change "Text" to something else?
> >
> > Thanks.
> >
> > PS: InstantDB is really a blast to work with!
> >
> >
> >
> >
> >
> -----------------------------------------------------------------------------
> To unsubscribe from this mailing list, send email to majordomo@enhydra.org
> with the text "unsubscribe instantdb" in the body of the email.
> If you have other questions regarding this mailing list, send email to
> the list admin at owner-instantdb@enhydra.org.
-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe instantdb" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-instantdb@enhydra.org.
|