1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317
//! # Passing parameters to statement //! //! ## In a nutshell //! //! * `()` -> No parameter //! * `a` -> Single parameter //! * `(a,b,c)` -> Fixed number of parameters //! * `&[a]` -> Arbitrary number of parameters //! * a.into_parameter() -> Convert idiomatic Rust type into something bindable by ODBC. //! //! ## Passing a single parameter //! //! ODBC allows you to bind parameters to positional placeholders. In the simples case it looks like //! this: //! //! ```no_run //! use odbc_api::Environment; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! let year = 1980; //! if let Some(cursor) = conn.execute("SELECT year, name FROM Birthdays WHERE year > ?;", year)? { //! // Use cursor to process query results. //! } //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! All types implementing the `Parameter` trait can be used. //! //! ## Annotating a parameter with an explicit SQL DataType //! //! In the last example we used a bit of domain knowledge about the query and provided it with an //! `i32`. Each `Parameter` type comes with a default SQL Type as which it is bound. In the last //! example this spared us from specifing that we bind `year` as an SQL `INTEGER` (because `INTEGER` //! is default for `i32`). If we want to, we can specify the SQL type independent from the Rust type //! we are binding, by wrapping it in `WithDataType`. //! //! ```no_run //! use odbc_api::{Environment, parameter::WithDataType, DataType}; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! let year = WithDataType{ //! value: 1980, //! data_type: DataType::Varchar {length: 4} //! }; //! if let Some(cursor) = conn.execute("SELECT year, name FROM Birthdays WHERE year > ?;", year)? { //! // Use cursor to process query results. //! } //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! In that case it is likely that the driver manager converts our anotated year into a string which //! is most likely being converted back into an integer by the driver. All this converting can be //! confusing, but it is helpful if we do not know what types the parameters actually have (i.e. the //! query could have been entered by the user on the command line.). There is also an option to //! query the parameter types beforhand, but my advice is not trust the information blindly if you //! cannot test this with your driver beforehand. //! //! ## Passing a fixed number of parameters //! //! To pass multiple but a fixed number of parameters to a query you can use tuples. //! //! ```no_run //! use odbc_api::Environment; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! let too_old = 1980; //! let too_young = 2000; //! if let Some(cursor) = conn.execute("SELECT year, name FROM Birthdays WHERE ? < year < ?;", (too_old, too_young))? { //! // Use cursor to congratulate only persons in the right age group... //! } //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! ## Passing an abitrary number of parameters //! //! Not always do we know the number of required parameters at compile time. This might be the case //! if the query itself is generated from user input. Luckily slices of parameters are supported, too. //! //! ```no_run //! use odbc_api::Environment; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! let params = [1980, 2000]; //! if let Some(cursor) = conn.execute( //! "SELECT year, name FROM Birthdays WHERE ? < year < ?;", //! ¶ms[..])? //! { //! // Use cursor to process query results. //! } //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! ## Passing the type you absolutly think should work, but does not. //! //! Sadly not every type can be safely bound as something the ODBC C-API understands. Most prominent //! among those is a Rust string slice (`&str`). //! //! ```no_run //! use odbc_api::Environment; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! // conn.execute("SELECT year FROM Birthdays WHERE name=?;", "Bernd")?; // <- compiler error. //! # Ok::<(), odbc_api::Error>(()) //! ``` //! ## Passing the type you absolutly think should work, but does not. //! //! Sadly not every type can be safely bound as something the ODBC C-API understands. Most prominent //! among those is a Rust string slice (`&str`). //! //! ```no_run //! use odbc_api::Environment; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! // conn.execute("SELECT year FROM Birthdays WHERE name=?;", "Bernd")?; // <- compiler error. //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! Alas, not all is lost. We can still make use of the `IntoParameter` trait to convert it into //! something that works. //! //! ```no_run //! use odbc_api::{Environment, IntoParameter}; //! //! let env = unsafe { //! Environment::new()? //! }; //! //! let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; //! if let Some(cursor) = conn.execute( //! "SELECT year FROM Birthdays WHERE name=?;", //! "Bernd".into_parameter())? //! { //! // Use cursor to process query results. //! }; //! # Ok::<(), odbc_api::Error>(()) //! ``` //! //! Conversion for `&str` is not too expensive either. Just an integer more on the stack. Wait, the //! type you wanted to use, but that I have conviniently not chosen in this example still does not //! work? Well, in that case please open an issue or a pull request. `IntoParameter` can usually be //! implemented entirely in safe code, and is a suitable spot to enable support for your custom //! types. use std::{convert::TryInto, ffi::c_void}; use odbc_sys::{CDataType, NULL_DATA}; use crate::{ handles::{CData, Input}, DataType, }; /// Extend the input trait with the guarantee, that the bound parameter buffer contains at least one /// element. pub unsafe trait Parameter: Input {} /// Annotates an instance of an inner type with an SQL Data type in order to indicate how it should /// be bound as a parameter to an SQL Statement. /// /// # Example /// /// ```no_run /// use odbc_api::{Environment, parameter::WithDataType, DataType}; /// /// let env = unsafe { /// Environment::new()? /// }; /// /// let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; /// // Bind year as VARCHAR(4) rather than integer. /// let year = WithDataType{ /// value: 1980, /// data_type: DataType::Varchar {length: 4} /// }; /// if let Some(cursor) = conn.execute("SELECT year, name FROM Birthdays WHERE year > ?;", year)? { /// // Use cursor to process query results. /// } /// # Ok::<(), odbc_api::Error>(()) /// ``` pub struct WithDataType<T> { pub value: T, pub data_type: DataType, } unsafe impl<T> CData for WithDataType<T> where T: CData, { fn cdata_type(&self) -> CDataType { self.value.cdata_type() } fn indicator_ptr(&self) -> *const isize { self.value.indicator_ptr() } fn value_ptr(&self) -> *const c_void { self.value.value_ptr() } fn buffer_length(&self) -> isize { self.value.buffer_length() } } unsafe impl<T> Input for WithDataType<T> where T: Input, { fn data_type(&self) -> DataType { self.data_type } } unsafe impl<T> Parameter for WithDataType<T> where T: Parameter {} /// Binds a byte array as a VarChar input parameter. /// /// While a byte array can provide us with a pointer to the start of the array and the length of the /// array itself, it can not provide us with a pointer to the length of the buffer. So to bind /// strings which are not zero terminated we need to store the length in a separate value. /// /// This type is created if `into_parameter` of the `IntoParameter` trait is called on a `&str`. /// /// # Example /// /// ```no_run /// use odbc_api::{Environment, IntoParameter}; /// /// let env = unsafe { /// Environment::new()? /// }; /// /// let mut conn = env.connect("YourDatabase", "SA", "<YourStrong@Passw0rd>")?; /// if let Some(cursor) = conn.execute( /// "SELECT year FROM Birthdays WHERE name=?;", /// "Bernd".into_parameter())? /// { /// // Use cursor to process query results. /// }; /// # Ok::<(), odbc_api::Error>(()) /// ``` pub struct VarChar<'a> { bytes: &'a [u8], /// Will be set to value.len() by constructor. length: isize, } impl<'a> VarChar<'a> { /// Constructs a new VarChar containing the text in the specified buffer. pub fn new(value: &'a [u8]) -> Self { VarChar { bytes: value, length: value.len().try_into().unwrap(), } } /// Constructs a new VarChar representing the NULL value. pub fn null() -> Self { VarChar { bytes: &[], length: NULL_DATA, } } } unsafe impl CData for VarChar<'_> { fn cdata_type(&self) -> CDataType { CDataType::Char } fn indicator_ptr(&self) -> *const isize { &self.length } fn value_ptr(&self) -> *const c_void { self.bytes.as_ptr() as *const c_void } fn buffer_length(&self) -> isize { 0 } } unsafe impl Input for VarChar<'_> { fn data_type(&self) -> DataType { DataType::Varchar { length: self.bytes.len(), } } } unsafe impl Parameter for VarChar<'_> {}