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]

st: -odbc- and VARCHAR() [was odbc load a large table, hitting max obs limit]


From   "Joseph Coveney" <jcoveney@bigplanet.com>
To   <statalist@hsphsun2.harvard.edu>
Subject   st: -odbc- and VARCHAR() [was odbc load a large table, hitting max obs limit]
Date   Mon, 10 Sep 2012 11:22:15 +0900

Dimitriy V. Masterov wrote (excerpted):

You need to recast the varchar variable as something that Stata can understand. 

--------------------------------------------------------------------------------

Is that peculiar to MySQL or Unix ODBC drivers or something?  I've never had any
problems with Stata and VARCHAR() column data types in MS SQL Server databases,
or even MS Access, for that matter.  Rows of VARCHAR() columns containing text
longer than 244 characters get automatically truncated, and those Unicode
characters in NVARCHAR() columns that cannot be coerced into ANSI become
question marks, but [N]VARCHAR() columns are otherwise read-in without any
problem.

Joseph Coveney


*
*   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