Hi there, Toddler,
May I recommend you change your naming conventions?
I would recommend you title your tables as they are, e.g.:
*SomeTable*
and then you title each field as:
*SomeTable.SomeField*
Why? Because...
1. there may be different tables with the same field
2. searching for th
Hi again, Toddler,
Yuo may even want to consider using the schema as a prefix, should you have
more than one, e.g.:
- schema
- schema.SomeTable
- schema.SomeTable.SomeField
Best wishes,
Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki
Tobias,
Thank you for the response and the link to the schema tiddly. The way that
template functions is really great. Your suggestion on changing the naming
convention is also a really good one.
However, the reasoning as to why a field would its own tiddler (independent
of the table) is becau
Hi Toddler,
I added a few more templates to: http://schema.tiddlyspot.com
> A Client_Number field will be the same whether it is on the Client_Table
> or the Account_Table.
>
Actually, I would think that in the client table it will probably be the
primary key, perhaps *ClientKey* where as in
Hi again, Toddler,
I modified the template showing other fields of the same table
to give you an example for revealing stuff using states, see...
http://schema.tiddlyspot.com
Best wishes,
Tobias.
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
Hi Again, Toddler...
So, to solve your original request you basically do need to have one field
per table in order to filter appropriately.
In other words, you need to drop the pattern of listing all Tables a Field
is being used in the Field tiddler.
Instead, everyon Table.Field tiddler should d
6 matches
Mail list logo
