- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 517 for Like (0.16 sec)
-
clause/expression.go
Gt(lte).Build(builder) } // Like whether string matches regular expression type Like Eq func (like Like) Build(builder Builder) { builder.WriteQuoted(like.Column) builder.WriteString(" LIKE ") builder.AddVar(builder, like.Value) } func (like Like) NegationBuild(builder Builder) { builder.WriteQuoted(like.Column) builder.WriteString(" NOT LIKE ") builder.AddVar(builder, like.Value) }
Go - Registered: Sun Apr 28 09:35:09 GMT 2024 - Last Modified: Tue Oct 10 06:45:48 GMT 2023 - 8.3K bytes - Viewed (0) -
docs/en/docs/advanced/openapi-callbacks.md
When implementing the callback yourself, you could use something like <a href="https://www.python-httpx.org" class="external-link" target="_blank">HTTPX</a> or <a href="https://requests.readthedocs.io/" class="external-link" target="_blank">Requests</a>. ## Write the callback documentation code This code won't be executed in your app, we only need it to *document* how that *external API* should look like.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Thu Apr 18 19:53:19 GMT 2024 - 7.7K bytes - Viewed (0) -
tests/distinct_test.go
t.Fatalf("errors happened when create users: %v", err) } var names []string DB.Table("users").Where("name like ?", "distinct%").Order("name").Pluck("name", &names) AssertEqual(t, names, []string{"distinct", "distinct", "distinct", "distinct-2", "distinct-3"}) var names1 []string DB.Model(&User{}).Where("name like ?", "distinct%").Distinct().Order("name").Pluck("Name", &names1)
Go - Registered: Sun Apr 28 09:35:09 GMT 2024 - Last Modified: Thu Jan 06 07:02:53 GMT 2022 - 2.5K bytes - Viewed (0) -
okhttp/src/main/kotlin/okhttp3/internal/http/RequestLine.kt
* http://android.com/foo HTTP/1.1") or only the path (like "GET /foo HTTP/1.1"). */ private fun includeAuthorityInRequestLine( request: Request, proxyType: Proxy.Type, ): Boolean { return !request.isHttps && proxyType == Proxy.Type.HTTP } /** * Returns the path to request, like the '/' in 'GET / HTTP/1.1'. Never empty, even if the request
Plain Text - Registered: Fri May 03 11:42:14 GMT 2024 - Last Modified: Mon Jan 08 01:13:22 GMT 2024 - 2K bytes - Viewed (0) -
dbflute_fess/playsql/_readme.txt
The "data" directory is for data loading like this: /- - - - - - - - - - - - - - - - - - - - playsql |-data |-common | |-xls | |-10-master.xls | |-defaultValueMap.dataprop |-ut |-xls |-20-member.xls |-30-product.xls |-defaultValueMap.dataprop - - - - - - - - - -/ The format of a xls file is like this: /- - - - - - - - - - - - - - - - - - - -
Plain Text - Registered: Mon Apr 29 08:04:11 GMT 2024 - Last Modified: Sat Jul 04 22:46:31 GMT 2015 - 1.3K bytes - Viewed (0) -
docs/en/docs/tutorial/encoder.md
# JSON Compatible Encoder There are some cases where you might need to convert a data type (like a Pydantic model) to something compatible with JSON (like a `dict`, `list`, etc). For example, if you need to store it in a database. For that, **FastAPI** provides a `jsonable_encoder()` function. ## Using the `jsonable_encoder` Let's imagine that you have a database `fake_db` that only receives JSON compatible data.
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Tue Oct 17 05:59:11 GMT 2023 - 1.8K bytes - Viewed (0) -
docs/en/docs/tutorial/first-steps.md
Plain Text - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Fri Jun 30 18:25:16 GMT 2023 - 9.2K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
Features like transitive dependencies and the new parent specification mechanism. The problem we run into is that currently we have information about a project scattered across the project.xml and the various properties files. What needs to be done is to encapsulate all of this in the POM. Typically users parameterize the use of plugins, or have custom values like ${user.name}
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
.github/pull_request_template.md
for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MNG-XXX] SUMMARY`, where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA issue.
Plain Text - Registered: Sun Apr 28 03:35:10 GMT 2024 - Last Modified: Tue Dec 20 13:14:27 GMT 2022 - 1.9K bytes - Viewed (0) -
docs_src/custom_response/tutorial008.py
Python - Registered: Sun Apr 28 07:19:10 GMT 2024 - Last Modified: Mon Jul 19 19:14:58 GMT 2021 - 360 bytes - Viewed (0)