public SqlBuilder GroupBy ( string sql, params object parameters ).
public SqlBuilder OrderB圜ols ( params string columns )./// Adds columns in the Order By clause.public SqlBuilder OrderBy ( string sql, params object parameters ).public SqlBuilder LeftJoin ( string sql, params object parameters ).public SqlBuilder Join ( string sql, params object parameters ).public SqlBuilder Select ( params string columns ).public SqlBuilder Where ( string sql, params object parameters ).The Where keyword still needs to be specified. For example, if UserDto also had a list of BoatsDto, only the CarDto list or the BoatsDto list can be loaded and mapped with one query. FetchOneToMany cannot be used to fetch nested one-to-many relationships, or multiple one-to-many relationships. In the above example this might be x => x.CarId.ĥ. This should return the property of the primary of the many object. If you are using an outer join for your query and you are expecting that some of the many's will not be populated, make sure to use the second lambda in the FetchOneToMany call. If you are mapping to objects that are also used for inserting data then you will need to make sure you ignore the List property using the attribute.Ĥ. In this example the query specifies u.* then c* which maps to. It must align with the order of the generic parameters defined. The order of the columns is extremely important. The first parameter to this method is a lambda expression which identifies the unique property of the first object.Ģ. This will give you a list of UserDto objects and for each of these the list of CarDto's will also be populated.ġ. "select u.*, c.* from Users u inner join Cars c on u.UserId = c.UserId order by u.UserId" ).IDatabase db = new Database ( "connStringName" ).To return the same results as the Pagemethod, the query would be as follows: The second parameter is the number of records to return after x number of records have been skipped. It has the same number of parameters as the Page method, but instead of the first parameter being the page number, it is the number of records to skip. The SkipTake method is very similar to the Skip and Take methods in LINQ. In the example above, the second page with 10 users in it will be returned. The second parameter is the size of the page. This number begins at 1 for the first page.
The first parameter to the Page method is the page number. Note: You must provide an order by statement in your SQL statement so that the query knows in which order you want your data to be paged. There is a NPoco.JsonNet library which allows you to use the JsonNetColumnSerializer. (v3+ only) Properties with the Serialized column attribute will serialize their data with the default serializer unless changed by implementing a IColumnSerializer. Properties with the Computed column attribute work the same way as the Result column attributes however they will be auto selected in the SQL. It will not be included in the auto generated SQL. Note: These columns will need to be explicitly specified in the SQL. Properties marked with the Result column can be mapped into, however these properties will not be included in inserts or updates. This property will be ignored and cannot be mapped to. This is used if the column name does not match the property name. For Oracle there is also a "sequenceName" property which will be used when inserting data with Oracle. There is also an "autoIncrement" property which is used to indicate whether the primary key column is auto incremented e.g. Multiple primary keys can be specified by separating the columns with a comma. This has a "columnName" parameter which takes the column name of the primary key for the table. This takes a "name" parameter which indicates the table for which the Poco class will be mapped to. It will be assumed that the table name will be the class name and the primary key will be 'Id' if its not specified with the attributes below.īasic mapping is done via attributes.
0 kommentar(er)
