Am 10.04.2016 22:15 schrieb "Mazola Winstrol" :
>
> 2016-03-07 3:53 GMT-03:00 Sven Barth :
>>
>> Am 06.03.2016 22:09 schrieb "Mazola Winstrol" :
>> >
>> > Hello,
>> >
>> > Fpc: 3.0
>> >
>> > Should the compiler to allow the definition of two operator
overloading with the same parameters and diferen
2016-03-07 3:53 GMT-03:00 Sven Barth :
> Am 06.03.2016 22:09 schrieb "Mazola Winstrol" :
> >
> > Hello,
> >
> > Fpc: 3.0
> >
> > Should the compiler to allow the definition of two operator overloading
> with the same parameters and diferent result types?
> >
> > e.g:
> >
> > code
> >
> >
Well, I guess if there is no user input going into the query it's not a big
dea,l of course if there is you should at least sanitize it to prevent
injection.
On Apr 10, 2016 2:39 PM, "Luiz Americo Pereira Camara" <
luizameri...@gmail.com> wrote:
>
>
> 2016-04-10 16:29 GMT-03:00 Tony Caduto :
>
>>
2016-04-10 16:29 GMT-03:00 Tony Caduto :
> What about using a stored procedure to do it ? You could pass the list
> for the in as a string and handle it in the stored procedure. Of course
> that's no help if using sqlite or other that does not support stored
> procedures.
>
I'm working with mul
What about using a stored procedure to do it ? You could pass the list for
the in as a string and handle it in the stored procedure. Of course that's
no help if using sqlite or other that does not support stored procedures.
On Apr 10, 2016 1:39 PM, "Stephen Chrzanowski" wrote:
The problem with
2016-04-10 15:39 GMT-03:00 Stephen Chrzanowski :
> Due to the nature of the bind mechanism, you won't be able to do it this
> way. The only way you'll be able to do that is with your program doing
> string substitution instead of doing the bind. Since you're dealing with
> integers only, you'll
2016-04-10 11:01 GMT-03:00 Tony Caduto :
> Did you try putting quotes around the param ID in the sql query?
> in(":myparam")
> I am guessing it's the commas that are the problem.
>
Its the other way around the problem is the quotes
See the attached app.
When using Select * from Test where Id in
The problem with that Tony is that the the bind might make :myparam a
string, so you'll be doing a 1-integer to 1-string comparison, which won't
give you any results. Essentially you'll be asking for a list of results
whos field is equal to "1,2,3,4", not a list of results in which the field
in qu
> I can confirm. Seems like is worth to put this on bugtracker :)
Reported here:
http://bugs.freepascal.org/view.php?id=29992
___
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
2016-03-28 17:49 GMT+02:00 Krzysztof :
> This code worked fine on FPC 2.6.4:
>
> procedure Test(constref AParam: String = 'def_param');
> begin
> writeln(AParam);
> end;
>
> But on FPC 3.0.0 I get error:
>
> unit1.pas(30,42) Error: Default values can only be specified for
> value, const and cons
Did you try putting quotes around the param ID in the sql query?
in(":myparam")
I am guessing it's the commas that are the problem.
Sqlite will accept double qoutes as will MySQL postgres will not though.
On Apr 10, 2016 7:40 AM, "leledumbo" wrote:
> > But until now i havent figured a way to pas
> But until now i havent figured a way to pass an array of values (mostly
integers) to be used with IN operators.
That, unfortunately, is not possible. It's a DBMS limitation, parameterized
values are actually passed as is to DBMS. So there's nothing you can do
unless you can convince DBMS maintai
I switched most of my SQL queries to use Params instead of formatting
directly the SQL.
But until now i havent figured a way to pass an array of values (mostly
integers) to be used with IN operators.
Example:
SQL: Select * from Customer where Id in (:idlist)
I need to query customers with Ids
13 matches
Mail list logo
