Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down on April 23, and its replacement, statalist.org is already up and running.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: could it be a bug in odbc??


From   Nick Cox <njcoxstata@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: could it be a bug in odbc??
Date   Thu, 30 Aug 2012 15:09:05 +0100

I don't think this kind of verbal paraphrase helps much with a
technical difficulty. It's exact code, exact file details, exact
responses from Stata that count.

Given the lack of response yesterday, I'd report this to Stata
technical support. See
http://stata.com/support/faqs/technical-support/ for how to contact
them and what they will expect, including your registration details.

Nick

On Thu, Aug 30, 2012 at 3:00 PM, tashi lama <ltashi32@hotmail.com> wrote:

 I posted this question yesterday and failed to hear any responses.
Could be because the way I framed my question. So, I am attempting to
make it more clear and concise. The problem is with odbc running in
unix. I have a table "readership" in mysql which has a column
doc_title of type varchar. While running in windows, odbc imports that
column in stata with data type string. This runs in par with the stata
documentation which lists string as the corresponding stata datatype
to varchar in SQL. The problem arises while running Stata in unix.
Stata skips the the column doc_title and gives the following notice.
> note: doc_title is of a type not supported in Stata; skipped
>
> This is so confusing. Did anyone encounter this problem? Any hint or solution will be highly appreicated.
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index