Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: st: -odbc- and VARCHAR() [was odbc load a large table, hitting max obs limit]
From
"Dimitriy V. Masterov" <[email protected]>
To
[email protected]
Subject
Re: st: -odbc- and VARCHAR() [was odbc load a large table, hitting max obs limit]
Date
Sun, 9 Sep 2012 20:16:56 -0700
I stand corrected. It looks like I can easily import varchars with
Teradata, 64-bit Stata on Linux, and unixodbc as my odbc manager. Some
other formats, like date intervals and spatial/GIS, do give me the
same error as Tashi.
DVM
On Sun, Sep 9, 2012 at 7:22 PM, Joseph Coveney <[email protected]> wrote:
> 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/
*
* 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/