Comments (11)
Do you prefer a CreateTable option, a CreateVirtualTable function, or alternatively, create normal tables and then add a virtual table for it. The problem with the latter is that maintenance is a bit annoying. Leaning towards CreateVirtualTable myself...
from sqlite-net.
Actually, I think I would prefer a TableAttribute with an IsVirtual bool property and a Using string property. The CreateTable code could then check for this and submit the different Create table statement.
Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or alternatively, create normal tables and then add a virtual table for it. The problem with the latter is that maintenance is a bit annoying. Leaning towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
I get it, except sometimes there are more parameters to track. For example,
I use
CREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]
wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual bool
property and a Using string property. The CreateTable code could then check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for it.
The problem with the latter is that maintenance is a bit annoying. Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
ColumnAttribute obviously. :-)
I've been meaning to add TableAttribute and ColumnAttribute with Name properties anyway, so this will be a good start.
Are the tokenizers a fixed set? If so, it would be nice to use an enum with nice names. Can we use CultureInfo for the Culture or are strings better?
Lastly, we will need a static class StringEx { public static bool Matches (string arg) { throw new NotSupportedException (); } } so that we can have Linq support. You can see how LIKE is handled in TableQuery. If you're not comfortable with this, then you can leave it to me.
Also, some tests would be best. What platform do you use?
-Frank
On Jun 28, 2012, at 2:24 PM, tofutim wrote:
I get it, except sometimes there are more parameters to track. For example,
I useCREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual bool
property and a Using string property. The CreateTable code could then check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for it.
The problem with the latter is that maintenance is a bit annoying. Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
Wait, tokenize is not really a column, it is some instruction to FTS4. It's
like the Rebuild command which is similarly goofy looking:
INSERT INTO verses(verses) VALUES ('rebuild');
On Thu, Jun 28, 2012 at 2:29 PM, Frank A. Krueger <
[email protected]
wrote:
ColumnAttribute obviously. :-)
I've been meaning to add TableAttribute and ColumnAttribute with Name
properties anyway, so this will be a good start.Are the tokenizers a fixed set? If so, it would be nice to use an enum
with nice names. Can we use CultureInfo for the Culture or are strings
better?Lastly, we will need a static class StringEx { public static bool Matches
(string arg) { throw new NotSupportedException (); } } so that we can have
Linq support. You can see how LIKE is handled in TableQuery. If you're not
comfortable with this, then you can leave it to me.Also, some tests would be best. What platform do you use?
-Frank
On Jun 28, 2012, at 2:24 PM, tofutim wrote:
I get it, except sometimes there are more parameters to track. For
example,
I useCREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual bool
property and a Using string property. The CreateTable code could then
check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for it.
The problem with the latter is that maintenance is a bit annoying.
Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
Tokenizer is not a fixed set - you can add your own into SQLite (we do...).
I'm using Windows right now (actually now to WinRT) but we do Windows,
WinRT, MonoDroid and and MonoTouch.
On Thu, Jun 28, 2012 at 2:31 PM, E. Timothy Uy [email protected] wrote:
Wait, tokenize is not really a column, it is some instruction to FTS4.
It's like the Rebuild command which is similarly goofy looking:INSERT INTO verses(verses) VALUES ('rebuild');
On Thu, Jun 28, 2012 at 2:29 PM, Frank A. Krueger <
[email protected]wrote:
ColumnAttribute obviously. :-)
I've been meaning to add TableAttribute and ColumnAttribute with Name
properties anyway, so this will be a good start.Are the tokenizers a fixed set? If so, it would be nice to use an enum
with nice names. Can we use CultureInfo for the Culture or are strings
better?Lastly, we will need a static class StringEx { public static bool Matches
(string arg) { throw new NotSupportedException (); } } so that we can have
Linq support. You can see how LIKE is handled in TableQuery. If you're not
comfortable with this, then you can leave it to me.Also, some tests would be best. What platform do you use?
-Frank
On Jun 28, 2012, at 2:24 PM, tofutim wrote:
I get it, except sometimes there are more parameters to track. For
example,
I useCREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual
bool
property and a Using string property. The CreateTable code could then
check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for
it.
The problem with the latter is that maintenance is a bit annoying.
Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
[Table(IsVirtual = true, Using = "FTS4")]
public class Verse {
[Column(Tokenizer = SQLiteTokenizers.Icu, Culture = "en_AU")]
public string Verse { get; set; }
public string A { get; set; }
public string B { get; set; }
public string C { get; set; }
}
On Jun 28, 2012, at 2:31 PM, tofutim wrote:
Wait, tokenize is not really a column, it is some instruction to FTS4. It's
like the Rebuild command which is similarly goofy looking:INSERT INTO verses(verses) VALUES ('rebuild');
On Thu, Jun 28, 2012 at 2:29 PM, Frank A. Krueger <
[email protected]wrote:
ColumnAttribute obviously. :-)
I've been meaning to add TableAttribute and ColumnAttribute with Name
properties anyway, so this will be a good start.Are the tokenizers a fixed set? If so, it would be nice to use an enum
with nice names. Can we use CultureInfo for the Culture or are strings
better?Lastly, we will need a static class StringEx { public static bool Matches
(string arg) { throw new NotSupportedException (); } } so that we can have
Linq support. You can see how LIKE is handled in TableQuery. If you're not
comfortable with this, then you can leave it to me.Also, some tests would be best. What platform do you use?
-Frank
On Jun 28, 2012, at 2:24 PM, tofutim wrote:
I get it, except sometimes there are more parameters to track. For
example,
I useCREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual bool
property and a Using string property. The CreateTable code could then
check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for it.
The problem with the latter is that maintenance is a bit annoying.
Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
Hmm, I like that.
On Thu, Jun 28, 2012 at 2:34 PM, Frank A. Krueger <
[email protected]
wrote:
[Table(IsVirtual = true, Using = "FTS4")]
public class Verse {
[Column(Tokenizer = SQLiteTokenizers.Icu, Culture = "en_AU")]
public string Verse { get; set; }
public string A { get; set; }
public string B { get; set; }
public string C { get; set; }
}On Jun 28, 2012, at 2:31 PM, tofutim wrote:
Wait, tokenize is not really a column, it is some instruction to FTS4.
It's
like the Rebuild command which is similarly goofy looking:INSERT INTO verses(verses) VALUES ('rebuild');
On Thu, Jun 28, 2012 at 2:29 PM, Frank A. Krueger <
[email protected]wrote:
ColumnAttribute obviously. :-)
I've been meaning to add TableAttribute and ColumnAttribute with Name
properties anyway, so this will be a good start.Are the tokenizers a fixed set? If so, it would be nice to use an enum
with nice names. Can we use CultureInfo for the Culture or are strings
better?Lastly, we will need a static class StringEx { public static bool
Matches
(string arg) { throw new NotSupportedException (); } } so that we can
have
Linq support. You can see how LIKE is handled in TableQuery. If you're
not
comfortable with this, then you can leave it to me.Also, some tests would be best. What platform do you use?
-Frank
On Jun 28, 2012, at 2:24 PM, tofutim wrote:
I get it, except sometimes there are more parameters to track. For
example,
I useCREATE VIRTUAL TABLE verses USING FTS4(verse, tokenize=icu);
Where would you keep or track "tokenize=icu"?
Also there is sometimes a locale
CREATE VIRTUAL TABLE names USING fts3(a, b, tokenize=icu en_AU);
On Thu, Jun 28, 2012 at 2:20 PM, Frank A. Krueger <
[email protected]wrote:
Actually, I think I would prefer a TableAttribute with an IsVirtual
bool
property and a Using string property. The CreateTable code could then
check
for this and submit the different Create table statement.Does that make sense?
On Jun 28, 2012, at 2:16 PM, tofutim wrote:
Do you prefer a CreateTable option, a CreateVirtualTable function, or
alternatively, create normal tables and then add a virtual table for
it.
The problem with the latter is that maintenance is a bit annoying.
Leaning
towards CreateVirtualTable myself...
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
Reply to this email directly or view it on GitHub:
#69 (comment)
from sqlite-net.
Has this feature been implemented?
from sqlite-net.
@supernova32 Not in the way described here by there is the CreateFlags
option on CreateTable to accomplish this.
Still need to implement the attribute.
from sqlite-net.
I would like to use tokenize=unicode61 "remove_diacritics=2".
Is there any alternatives?
from sqlite-net.
Related Issues (20)
- Getting RTL/Arabic Text from sqliteDB using this library flips character
- System.DLLNotFoundException:e_sqlcipher assembly:<unknown assembly> type:<unknown type> member:(null) HOT 1
- Insert large data (over 2GB) occurs OverflowException, how to solve it?
- SQLite version and how to upgrade it HOT 1
- Query with Where() returns no results, fails only with UWP release build
- Support for ORDER BY CASE WHEN? HOT 1
- SQLiteAsyncConnection Support for REGEXP
- LINQ Where() Does Not Work Well With Enums Decorated With the StoreAsTextAttribute
- Problem with .NET MAUI Blazor SQL app
- Debug local iphone result in file is not a database HOT 1
- Android 10 release version results in file is not a database error HOT 1
- Cannot get SQL for: Subtract
- e_sqlite3.dll not included in single file output with Native AOT compilation HOT 2
- Exception: Library e_sqlite3 not found, is seen when application is run in x64 or AnyCPU.
- "Where" clause doesn't work with bool when record is migrated until the record is updated
- e_sqlite.dll is created but not showing an error when using it.
- Using sqlite-net-base with SQLitePCLRaw.provider.winsqlite3 HOT 2
- The UniqueAttribute is not used in the DDL
- Using versions that support standard .net in an old .NET 4.X project doesn't work
- ExecuteAsync and RunInTransactionAsync are not safe together. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sqlite-net.