New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
如何保存byte[]数组到数据库,不定长 #63
Comments
用的是SQLite |
base64编码成字符串存到数据库.取得以后在base64解码
获取 Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: rote667668 <notifications@github.com>
Sent: Saturday, June 9, 2018 12:03:54 PM
To: sunkaixuan/SqlSugar
Cc: Subscribed
Subject: Re: [sunkaixuan/SqlSugar] 如何保存byte[]数组到数据库,不定长 (#63)
用的是SQLite
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#63 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AY2qVsNgJhpgeE83zXG83NWawOJMgM6Dks5t60kqgaJpZM4UhKdy>.
|
@lpyedge 我每条数据10K的byte,每条都要这样转,岂不是很影响效率 |
效率?你每秒读写能超过多少次?如果读写次数不高的话这点效率损失基本可以忽略.要看使用场景的.否则你就要用缓存来读写了.话说回来,都用sqlite了基本可以肯定你那边不会有效率问题的
获取 Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: rote667668 <notifications@github.com>
Sent: Saturday, June 9, 2018 2:04:52 PM
To: sunkaixuan/SqlSugar
Cc: lpyedge; Mention
Subject: Re: [sunkaixuan/SqlSugar] 如何保存byte[]数组到数据库,不定长 (#63)
@lpyedge<https://github.com/lpyedge> 我每条数据10K的byte,每条都要这样转,岂不是很影响效率
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#63 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AY2qVqovqCxWnGhMD3teHzb3qrut3pb2ks5t62WEgaJpZM4UhKdy>.
|
@lpyedge 说的很有道理 我先这么试试,以后不行了再研究,谢谢你 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
新手用SqlSugar,请帮助我谢谢!
定义了个数组
[SugarColumn(IsNullable = true)]
public byte[] Histo { get; set; }
直接给他赋值了别的数组 Histo = new byte[10]{1,2.3,4,5,6,7,8,9,10}
然后执行sqlClient.Insertable(dbTestRst).ExecuteCommandAsync();发现Histo这个数据列并没有数据是空的,我应该如何操作数组写入数据库?
The text was updated successfully, but these errors were encountered: