I have a table :
Table foo( col1 integer primary key, *col2 int*, col3 text )
And I want to be able to change this to :
Table foo( col1 integer primary key, *col2 text*, col3 text )
I want to do this, because I have an enum in col2 and want to be able
to use custom collate function and
I was trying to download sources for Windows platform. However, it
seems fine now. Wonder what was the problem yesterday. :)
Thanks,
-Sandeep.
[EMAIL PROTECTED] wrote:
Marten Feldtmann [EMAIL PROTECTED] wrote:
And the dll is ok ???
That is unclear. I do not have good internet
Did you update the sources on sqlite.org/download.html ? I got a few
more files that were different from sqlite3.3.10 apart from sqlite3.h
and os_win.c ( fts1.c, os_win.c, parse.c, vdbe.c and where.c )
-Sandeep
[EMAIL PROTECTED] wrote:
Sandeep Suresh [EMAIL PROTECTED] wrote:
I got
I got sqlite-source-3.3.11.zip from sqlite.org/download.html and found
this issue. Seems incomplete to me going by http://sqlite.org/changes.html
Thanks,
-
To unsubscribe, send email to [EMAIL PROTECTED]
Nikki Locke wrote:
Joe Wilson wrote:
Looks reasonable. Consider filing a ticket with your patch.
A few make test tests that rely on the old short name behavior
for SELECT * with joins will report failure. Whether the old way is
necessarily correct in some tests is a matter of debate.
){
+if( longNames || pTabList-nSrc1 ){
pNew = sqlite3ExprListAppend(pNew, pExpr, pExpr-span);
}else{
pNew = sqlite3ExprListAppend(pNew, pExpr, pRight-token);
Thanks,
Sandeep
Sandeep Suresh wrote:
When doing a select with join as :
select * from table_1
left
When doing a select with join as :
select * from table_1
left join table_2
on table_1.column11 = table2.column21
column names are *not *qualified with table names. Instead, what I get
is column11, column12, column21, column22 and so on. ( where column11,
column12 are from table_1 and
Hi all,
To give a brief context : I'm trying to perform an upgrade from
db_old to db_new. db_old and db_new have almost the same tables with a
few modified columns.
Steps to reproduce the issue :
1. Opened database file db_new
2. Attached database file db_old as 'db1'
3. Perform insert
Thanks for the reply Richard... Ill try this !
-Sandeep
[EMAIL PROTECTED] wrote:
Sandeep Suresh [EMAIL PROTECTED] wrote:
Hi all,
The problem is for one of the columns that have values ( 8209454,
1254234, 1245663 ) in db_old, the values in the new database are changed
