On Wed, Mar 21, 2012 at 3:34 AM, LacaK <[email protected]> wrote: > > > > No. > Anyway, I change the colum names (id,name to col1, col2) > The error is: > "Cannot insert the value NULL into column 'col', table tempdb.dbo.#t..." > > > This error has nothing to do with FPC or SQLDB. > > Your SQL statement is trying to insert NULL in a required field. > > > No Michael, see the example I wrote before. > > Create table: > create table #t (col1 int, col2 varchar(60)) > > OBS: No column is required. > > This INSERT works: > insert into #t values (1, 'bla bla bla') > > This INSERT do NOT works: > insert into #t (col2) values ('bla bla') > > > > > Marcos, can you please test with explicitly allowed nulls: > create table #t (col1 int NULL, col2 varchar(60) NULL) > > (MS SQL Server nullability is controled by database setting "ANSI null > default" so you can check this setting on your temp database also) > L.
Yes, of course... you're right. I have this code that worked before so, I thought something broked. I had tested before in a different machine with other installation of MSSQL. My mistake, sorry. If I find some problems I can post in bugtracker or still early to do this? -- Michael, sorry for your time. Marcos Douglas _______________________________________________ fpc-devel maillist - [email protected] http://lists.freepascal.org/mailman/listinfo/fpc-devel
