fix this. To be honest, I'm not very familiar with sqlite's codebase, so the P3_STATIC is kind of a guess, but it compiled
and ran just fine. The reason this pragma is important to me is for compatibility with existing codebases. I have a couple large
applications that run on postgres, that I am porting to a desktop application that will use sqlite as the backend. I would rather
not add as aliases to all of the selects in these applications, so short_column_names is exactly what I want. I noticed there
was a FIX ME comment to remove those pragmas...
John
diff -NU3 -r ./select.c ../../sqlite-orig/src/select.c
--- ./select.c 2004-06-19 11:31:48.778990400 -0600
+++ ../../sqlite-orig/src/select.c 2004-06-17 13:03:38.000000000 -0600
@@ -739,7 +739,7 @@
sqlite3SetString(&zName, zTab, ".", zCol, 0);
sqlite3VdbeSetColName(v, i, zName, P3_DYNAMIC);
}else{
- sqlite3VdbeSetColName(v, i, zCol, P3_STATIC);
+ sqlite3VdbeSetColName(v, i, zCol, 0);
}
}else if( p->span.z && p->span.z[0] ){
sqlite3VdbeSetColName(v, i, p->span.z, p->span.n);--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
