Maurilio Longo wrote:
>
> But, :some_var could be a problem because it is the way in which you
> reference
> a method property inside a with object clause.
>
> So, maybe, we could end up with a different prefix which is then
> translated in
> the .c low level interface.
>
> I mean
>
> with object oObj
> ...
> text into cSql
> select * from mytable where key = :some_var
> enddtext
> ...
> end
>
I don't see any problems. In this case we can use alternative syntax
with object oObj
...
text into cSql
select * from mytable where key = @some_var
enddtext
...
end
Because we can see in SQLITE3 docs: In the SQL strings input to
sqlite3_prepare_v2() and its variants, literals may be replace by a
parameter in one of these forms:
?
?NNN
:AAA
@AAA
Maurilio Longo wrote:
>
> I think that we could restrict what is accepted by this new bind_all()
> function.
>
What you think abou
insert into t1( name, age) values( :name, ?7 )
sqlite3_bind_all( stmt, {'Mary', 'name', SQLITE_TEXT}, {19, 7,
SQLITE_INTEGER} [, ...] )
or
sqlite3_bind_all( stmt, {{'Mary', 'name', SQLITE_TEXT}, {19, 7,
SQLITE_INTEGER}} )
or
sqlite3_bind_all( stmt, { 'name', 7 }, { SQLITE_TEXT, SQLITE_INTEGER},
"Mary", 19, "Andi", 17 [, ...] )
or
??
Regards,
Petr
--
View this message in context:
http://www.nabble.com/Re%3AExperiences-with-sqlite--tp14791570p14806830.html
Sent from the Harbour - Dev mailing list archive at Nabble.com.
_______________________________________________
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
