Two data types in the one field?

In a database is it possible to have two data types in the one field?

For a currency field, can a small text identifier be included in this
field to differentiate between several identical sums.?

Peter Jason wrote:
In a database is it possible to have two data types in the one field?

For a currency field, can a small text identifier be included in this
field to differentiate between several identical sums.?

Only if the field is defined as a string I.e. VARCHAR. But then that's not
very useful as then you can't do queries based on value comparison like
give me all rows 100.

You're best to add an additional column with the descriptor.

In article ,
says...

In a database is it possible to have two data types in the one field?

For a currency field, can a small text identifier be included in this
field to differentiate between several identical sums.?

I'd guess you're starting to develop a database, or maybe this is a
college-related question?

You need to know about the existence of the topic of "normalisation".
Generally, it's the process of analysing what you want to store in such
a way as to give the maximum flexibility in manipulating and querying
that data. It tends to lead to more columns, and more rows, than a
newcomer might expect. If you get the table design right then
everything that follows is an order of magnitude easier. You'd only
deviate from the basic rules ("normal forms") if performance is an issue
in a very large database.

So if, for example, you wanted to store a currency value but for more
than one currency (dollar, euro, etc) you'd normally have a separate
field for the currency type.

Normalisation is one of those things that can be initially baffling, but
once you "get it", it suddenly seems obvious!

I've cast about for a good introduction - this might be of interest:
https://www.youtube.com/watch?v=vIsO34Ei1-4

--

Phil, London